# emerge -pqv www-client/chromium [ebuild U ] www-client/chromium-59.0.3071.86 [58.0.3029.110] USE="cups gtk3* hangouts (pic) proprietary-codecs system-ffmpeg tcmalloc -component-build -custom-cflags -gconf -gnome-keyring -kerberos (-neon) -pulseaudio (-selinux) -suid (-system-libvpx) {-test} -widevine" L10N="-am -ar -bg -bn -ca -cs -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" [blocks B ] <sys-apps/sandbox-2.11 ("<sys-apps/sandbox-2.11" is blocking www-client/chromium-59.0.3071.86) # emerge -pqv '>=sys-apps/sandbox-2.11' [ebuild U ] sys-apps/sandbox-2.11-r5 [2.10-r4] ABI_X86="(32) (64) x32" The following mask changes are necessary to proceed: (see "package.unmask" in the portage(5) man page for more details) # required by >=sys-apps/sandbox-2.11 (argument) # /var/db/portage/repos/gentoo/profiles/package.mask: # Ian Stakenvicius (17 Nov 2016) # Does not honour LD_LIBRARY_PATH set in the environment, causing # all mozilla packages to fail in src_install() when xpcshell is # called in ${WORKDIR}, #580726 # Segfaults when creating directories #578582 =sys-apps/sandbox-2.11-r5
Upstream issue [0] would indicate that this happens for a good reason. [0]https://bugs.chromium.org/p/chromium/issues/detail?id=586444
(In reply to Jouni Kosonen from comment #1) > Upstream issue [0] would indicate that this happens for a good reason. > > [0]https://bugs.chromium.org/p/chromium/issues/detail?id=586444 I'm sure the mask is there for a good reason. My complaint is that Portage is not smart enough to avoid trying to upgrade www-client/chromium when this block exists, so probably there should be a package.use.mask on "tcmalloc" in >=www-client/chromium-59.
(In reply to Matt Whitlock from comment #2) > there should be a package.use.mask on "tcmalloc" in >=www-client/chromium-59. D'oh! There already is just such a use mask. My issue was that I had manually unmasked it quite some time ago for all versions of chromium. So this bug report is invalid. Sorry. :(
