The first release of Chromium 154 was announced recently and still, Google’s CI is failing to produce a source tarball.
Every recent release contained fixes for a shitload of CVE’s and it is unacceptable that I was unable to build packages because of missing source code. I waited and asked the developers, and received meaningless answers, and eventually had enough of the bullshit and fixed my ‘fetch-chromium-release.sh‘ script which I ship as part of the chromium SlackBuild.
The fetch script produces a real chromium source tarball now, similar sized to the official source tarball and I have used it to build a working package for Chromium 153 and now also for Chromium 154.
I posted the fetch script and also a somewhat expanded version ‘create-chromium-release-tarball.sh‘ which you can run as a cron job, to the Slackware Forge: https://forge.slackware.nl/alienbob/randomstuff/src/branch/main/chromium-scripts
At least now, when I wake up and there was a new Chromium release, I will find the tarball ready to use on my build server.
The chromium-154.0.8037.57 package is available in my repository now, and I am compiling chromium-ungoogled next.
I hope the scripts will help some of you.
Cheers, Eric
Thanks Eric for your effort and time to compile chromium. I appreciate it.
Thanks again for your work (gymnastics!) to keep chromium and ungoogled-chromium up to date.
ungoogled-chromium 154.0.8037.92 running and behaving itself here
Thanks! It is always nice to see the chromium ungoogled float by on the slackpkg upgrade-all
Thanks for the new chromium-ungoogled 155.0.8059.39 update!
Only 247 security fixes this time. Can they not run AI on the code before they publish it?