chromium-bin is statically linked to icu 4.4 % ldd /opt/chromium.org/chrome |grep 'not found' libicui18n.so.44 => not found libicuuc.so.44 => not found However the ebuild simply has RDEPEND=>=dev-libs/icu-4.4.1 so that when icu-4.6 became available chromium stopped working. adding '>=dev-libs/icu-4.5' to package.mask fixed this Reproducible: Always
If chromium-bin is never going to be in ARCH (stabilized), then the build root should be all ~arch too. I didn't look at the dates of the packages involved here, if the build root is all ~arch already, then the -bin package just needs to be rebuilt.
*** Bug 347147 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > If chromium-bin is never going to be in ARCH (stabilized), then the build root > should be all ~arch too. For now I adjusted the dependency. I think chromium-bin should be stabilized at some point. For now the build roots are arch (stable). Anyway, when it was built there was no icu-4.6. I'll keep the bug open, and think about the right solution. One possibility would be to use bundled icu for chromium-bin. That doesn't solve the general problem though, because all libraries at some point break binary compatibility. Another option is having two build roots.
Fixed with the bump to 8.x.