Google Chrome is a pre-compiled binary, and there is no way for me to recompile it. Would it be possible to add a slotted version of the libgcrypt package that would only install libgcrypt.so.11?
Breaks media-sound/spotify, too... Stupid binaries.
Add app-emulation/vmware-workstation and app-emulation/vmware-player to the list...
Add sys-power/suspend as well
*** Bug 494682 has been marked as a duplicate of this bug. ***
(In reply to Ted Tanberry from comment #3) > Add sys-power/suspend as well This is source package (with build failure tracked in bug #494488), not a pre-compiled one.
(In reply to Nikos Chantziaras from comment #2) > Add app-emulation/vmware-workstation and app-emulation/vmware-player to the > list... Does it really break vmware-player? It was my only package that was keeping Portage from removing libgcrypt.so.11 (by means of preserved-rebuild) but as I knew that vmware-player installs the /opt/vmware/lib/vmware/lib/libgcrypt.so.11/libgcrypt.so.11 file, I simply removed the package and then re-emerged it. My system libgcrypt.so.11 was removed by Portage and vmware-player simply started using its own bundled copy and it seems to work just fine.
(In reply to Bartosz Brachaczek from comment #6) On a second thought though, it might make sense to make vmware-{player,workstation} depend on the slotted package providing libgcrypt.so.11 so that it could receive potential security fixes. But I guess this issue is orthogonal to this bug report, I'm done spamming you guys ;)
+ 25 Dec 2013; Mike Gilbert <floppym@gentoo.org> + google-chrome-31.0.1650.63_p1.ebuild, google-chrome-32.0.1700.68_beta1.ebuild, + google-chrome-33.0.1750.5_alpha1.ebuild: + Bundle a copy of libgcrypt, bug 494596.
after today's google-chrome-31.0.1650.63_p1.ebuild update, emerge still complains. * GNU in directory index is up-to-date. !!! existing preserved libs: >>> package: dev-libs/libgcrypt-1.6.0 * - /usr/lib64/libgcrypt.so.11 * - /usr/lib64/libgcrypt.so.11.8.2 * used by /opt/google/chrome/chrome (www-client/google-chrome-31.0.1650.63_p1) I guess its expected.