Someone asked how I am creating Chromium (also -ungoogled) packages these days? When you download my SlackBuild script and attempt to build the package yourself, the script will error out because it cannot download the sources.
For weeks now, the Google automation is broken with regards to creating Chromium source tarballs. Apparently some bug prevents their CI/CD pipelines from succeeding. This is reportedly fixed for the Chromium 132.x releases (currently their Beta versions) but Chromium 130 and now also 131 releases are announced without their accompanying source tarballs.
I have therefore created a script which fetches the needed stuff from git and packs that into a “chromium-$VERSION.tar.xz” tarball. You will find it in the “build” directory and it’s called “fetch-chromium-release.sh“. You run that script with a Chromium official version number, wait a long long time, and you end up with the 6+ GB source tarball which you can then move into your local “build” directory.
Hope that clarifies things and helps you compile chromium or chromium-ungoogled yourself.
Have fun! Eric
Thanks Eric!
Thanks!
Does XZ only compress it from 7 (as mentioned in your script) to 6 GB?
Seems strange to me. In your answer to me you wrote you need at least 30 GB of free diskspace.
Don’t trust the numbers I mention in that script. I wrote them down before I actually made all of it work. Run the script and then look at the directory sizes – I had already deleted those sources before I thought, it would be interesting to know what was the actual uncompressed size again?
I checked today: the total size of the source directory tree is 24 GB.
Thanks!
Thank you for all your hard work Eric. It is greatly appreciated!
Tarballs are available again.
Thu Dec 12 07:14:34 UTC 2024
chromium-ungoogled: updated 64bit to 131.0.6778.139 (Slackware 15.0 & onwards).
Thanks!
How did you do that, it was only released three hours ago!
Ah, I see you didn’t wait for the official merge. š
The worst that could happen is that they would find something else to update, but then I would simply have started over with building a package.
The changes were trivial and one sign-off was already given, so I had a good level of trust.
The two vulnerabilities with a criticality label of “High” that were fixed in this Chromium release were compelling enough that I wanted to build the ungoogled package ahead of the official tarball.
Makes sense.
Plus it already said there were no changes on their side.
Thanks!
No ‘notable changes’.