Chromium has a new major release with many critical security fixes that has been in the Arch repos since more than 14 days, a new minor release has been pushed yesterday.
Why is Firefox getting pushed to the stable branch, although 82.0 was just released yesterday?
Are there dependency problems with Chromium 86 and the current Manjaro stable branch?
Fast tracking browsers, requires them to be built for every branch. So if a Chromium update is needed in Stable and Testing branches the Team has to build it once for testing branch and then once for stable branch aswell, since the branches use different versions of the library dependencies.
So it requires a team member having time to maintain those when needed.
Apparently so!
But still, it would be nice if that process be continued. Fast tracking of security updates is very important. Moreover the Manjaro website very prominently displays the chart and claims boldly that fast tracking of security packages is done.
The latest build of Chromium can always been found here. Simply extract the ZIP-archive and execute the chrome binary. Currently I started to build Chromium on my rig for stable branch, which takes a lot of time. Normally I’ve no time to do any security-updates like this. So if people complain always about security updates, maybe they should consider to get active and join the team and get into packaging …
I tried yesterday to update Chromium buy compiling it on my workstation. After 4 hours my PC froze. Firefox takes 120 mins to compile on the same rig. So it is not our goal to spend a lot of time only to update Chromium …
What happens with: sudo pacman -U https://mirror.easyname.at/manjaro/pool/sync/chromium-86.0.4240.111-2-x86_64.pkg.tar.zst
If it works without issues, we can forward that build from testing to stable as an overlay.