The latest release of the Chromium source code (version 126.0.6478.182 was made available on July 16th) addresses several vulnerabilities as usual, some of which are rated as ‘High’ but none ‘Critical’ and also no new 0-days are reported.
You can fetch my Slackware 15.0 and -current packages both for chromium and (hopefully soon, because its source has not been released yet) also chromium-ungoogled . You may prefer one of the mirror servers (like my own US server and in a short while, the UK mirror) in case my primary slackware.nl server is not responding or too slow.
I am slowly transitioning back from being a caregiver for my mother (which absorbed me completely for 10 months) to a life where I have time and energy in the evenings to hack on Slackware again. You will soon find the next installment in the Slackware Cloud Server series here on the blog – an article dedicated to building a Docker stack as cloud storage backend for the open source Ente Auth 2-factor authentication app.
Cheers, Eric
Thanks Eric for your commitment. Good to hear things are getting better again.
The chromium-ungoogled source is available now, by the way.
Cheers, Marco
Thanks for the chromium-ungoogled 128.0.6613.84 update!
Another zero day.
Thanks for the chromium-ungoogled 129.0.6668.58 update!
Just a heads up for building the next Ungoogled Chromium, this patch (which is merged today):
https://github.com/ungoogled-software/ungoogled-chromium/pull/3072
adds 27 new locales, which, by my estimation, makes the package about 50 MB larger.
If you don’t want that you have to exclude it I think.
Cheers, Marco
If the added language packs are that big, I could split them off into a ‘l10n’ sub-package.
That’s uncompressed of course, sorry.
I see a package size increase of 3 MB – that’s less than 3% of the 115 MB total. I’ll leave it as-is.
Fair enough. Compared to plain Chromium it diverges more and more though. Changes that have nothing to do with privacy enhancement or being ungoogled. Most things I agree with, this one not.
I hear you. It has been a growing annoyance.
Thanks for the Chromium ungoogled 131.0.6778.69 update!
Did you use the copy script to checkout the Chromium 131 source, as apparently there is no tarball available?
I have added a script “fetch-chromium-release.sh” in the source directory which will generate a chromium release tarball for you – just provide a release number as its only argument, like “131.0.6778.69”. You might want to redefine TMP to a directory which has 30 GB of free storage space.
It looks like official source tarballs will not be available until the release of 132.x due to some CI bug.