@sparklepanic@infosec.exchange
2026-09-26 02:23 UTC
looks like im gonna have to switch to firefox on gentoo now,,,,
!!! The following installed packages are masked:
- www-client/chromium-151.0.7922.169-r1::gentoo (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# Sam James (2026-09-24)
# Increasingly challenging to maintain with increased release cadence,
# upstream toolchain changes, and conflicts between trying to provide
# a consistent experience for Gentoo users (avoiding bundled where possible)
# vs. getting updates out in a timely manner. Many unfixed vulnerabilities.
#
# Keeping it in ::gentoo isn't a matter of just supplying an updated ebuild,
# but a commitment to keeping it up to date and finding a compromise between
# users' expectations (like various USE flags & not forcing all bundled
# components) and maintainability.
#
# Still supported packages include:
# www-client/google-chrome variants
# Other chromium-based browsers:
# www-client/microsoft-edge
# www-client/opera
# www-client/vivaldi
# qtwebengine-based browsers (uses chromium's engine):
# kde-apps/konqueror
# www-client/falkon
# www-client/qutebrowser
# Other browsers:
# www-client/firefox and www-client/firefox-bin
# www-client/seamonkey
#
# Removal on 2026-10-24. Bug #982204.
Replies (1)
-
@alwayscurious@infosec.exchange 2026-09-28 05:07
@sparklepanic@infosec.exchange Not surprised. The only practical way to ship Chromium is to just use the upstream tarball with everything bundled. Yes, even the prebuilt clang. The advantage of doing things this way is that one gets a build under a FOSS license without Google integration.