as the summary said, the sphinx3 package is very f-ed up as it installs /usr/lib/libutil.so thus nuking the standard libutil.so provided by glibc in the case of poor Felix, his openssh is all screwed up now
hrm, other problems: - the src_unpack is outdated, remove it and dont inherit gnuconfig_update - USE=static is completely wrong, remove it (and thus remove src_unpack)
ive gone ahead and package.mask-ed this due to the severity of the bug
Some suggestions on how to fix a screwed up system? For now I recreated the links /usr/lib/libutil.so -> ../../lib/libutil.so.1 and /usr/lib/libutil.so.0 -> ../../lib/libutil.so.1, This is enough to start some apps but doesn't fully solves the issue, (for sure some app are now asking for /usr/lib/libutil.la during emerge,probably cause some dependancies were built against that trash) so I tried an "emerge -1 glibc". Still is not enough,I did a row of revdep-rebuild: "revdep-rebuild --pretend --ignore --library libutil.so" "revdep-rebuild --pretend --ignore --library libutil.so.0" "revdep-rebuild --pretend --ignore --library libutil.la" (probably there was a better way but I was a bit in a hurry) Discovering that all my kde apps were linked against libutil.so.0 and nothing was linked against the other 2. So I'll end with a: "revdep-rebuild --library libutil.so.0" Also, maybe a warning of some kind to anyone using/who emerged sphinx3 could be useful.
ops, sorry , correction, not all my kde packages but just 18 of them, phew....
read this: http://bugs.gentoo.org/show_bug.cgi?id=145550#c19
That's not enough for kde packages linked to /usr/lib/libutil.so.0 cause this file belongs to sphinx but not to glibc. A: #rm -f /usr/lib/libutil.so.0 ; revdep-rebuild --library libutil.so.0 fixes all.
Created attachment 97218 [details, diff] sphinx3-0.6-libutil.patch Raw patch for this issue, ebuild to follow (patch isn't enough)
Created attachment 97219 [details] sphinx3-0.6-r1.ebuild Ebuild that will emerge the package with /usr/lib/libsphinxutil.* instead. not tested if sphinx works fine after this intervent (well, it should, please test). NOTE: NEEDS to be applied in a sane environment.... if you already have sphinx3 you need to do: #emerge -C sphinx3 ; emerge -1 glibc ; revdep-rebuild --library libutil.so.0 before emerging new version.
has anyone considered adding this to portage? I had this problem break gnupg and it seems silly that an sync done on the 20th would have given me a known broken ebuild. It just seems that even if the patch here wasn't perfect it prevents breaking a pretty important library.... still the patch hasn't made it to portage. FWIW
*** Bug 149295 has been marked as a duplicate of this bug. ***
am looking at this -- there is a new version of sphinx3 which I am testing right now.
I committed sphinx3-0.6.3 to portage after testing it with colission-protect in features to be sure it doesn't overwrite anything. Let me know if I can remove it from package.mask.
ive cleaned up the 0.6.3 a bit once you remove the broken ebuilds (aka everything older than 0.6.3) then you can remove it from p.mask
I have removed the old ebuilds and removed this from p.mask. This bug is being closed.
*** Bug 154390 has been marked as a duplicate of this bug. ***
