[gentoo-amd64] Re: revdep broken x11-drivers/ati-drivers net-nds/openldap

[Duncan]

"Daiajo Tibdixious" <daiajo@×××××.com> posted
a4a9bfcb0701300443jc3ada1m5d15277d8bc0b5f3@××××××××××.com, excerpted
below, on  Tue, 30 Jan 2007 23:43:05 +1100:

> I've expanded
> the revdep-rebuild output with qfile information.
>
> x11-drivers/ati-drivers
>     usr/lib32/xorg/modules/dri/atiogl_a_dri.so
>     /usr/lib32/xorg/modules/dri/fglrx_dri.so
>         media-libs/mesa (/usr/lib64/opengl/xorg-x11/lib/libGL.so.1)
>         x11-drivers/ati-drivers (/usr/lib32/opengl/ati/lib/libGL.so.1)
>         x11-drivers/ati-drivers (/usr/lib64/opengl/ati/lib/libGL.so.1)
>         x11-libs/libX11 (/usr/lib64/libX11.so.6)
>         x11-libs/libXext (/usr/lib64/libXext.so.6)
>         sys-libs/libstdc++-v3 (/usr/lib64/libstdc++-v3/libstdc++.so.5)
> net-nds/openldap-2.3
>     /usr/lib64/libldap-2.2.so.7 net-nds/openldap-2.2-28-r7? liblber-2.2.so.7)
>     /usr/lib64/libldap.so.2.0.130 net-nds/openldap-2.2-28-r7? liblber.so.2)
>     /usr/lib64/libldap_r-2.2.so.7 net-nds/openldap-2.2-28-r7? liblber-2.2.so.7)
>     /usr/lib64/libldap_r.so.2.0.130 net-nds/openldap-2.2-28-r7? liblber.so.2)
>
> Firstly ati-drivers shows 2 broken .so's. I can't tell if libGL.so.1
> is the mesa one or the ati-drivers one, both are present. libX11,
> libXext, libstdc++-v3 are all present, so I don't know why
> revdep-rebuild is showing a breakage.
>
> If ati-drivers was broken, why is my graphics working?

Why is it working?  Because the part that's broken is 32-bit (if it's the
stuff in lib32, anyway), and the main system is 64-bit, which isn't
broken.  As long as you aren't trying to run any 32-bit games that use
the broken bit or something, you're probably fine.  Also note that even if
it's the 64-bit stuff, it's likely the 3D/OpenGL stuff, which most stuff
won't be using.  It'd only be used for 3D games, OpenGL screensavers, and
anything else OpenGL based you may be running.

This case is probably an example of one of the issues with
revdep-rebuild, or more precisely with binary-only packages you may
choose to run. Revdep-rebuild sees and scans the shared libraries, and
doesn't know when they are part of a binary-only package. Naturally, you
can remerge the binary-only package all day and if it was built against a
library not on your system, it's not going to help one bit.

Newer revdep-rebuild versions have a way to configure it to ignore certain
packages. If you have the /etc/revdep-rebuild/ dir with 99revdep-rebuild
inside, take a look at the comments in that file, and if you wish, you can
either modify it or create your own file in the dir with an appropriate
entry masking the problem dirs or individual libraries as necessary.  If
you don't have that dir, you probably need a newer (and possibly still
~arch, I've not checked) revdep-rebuild.  Of course this gets
revdep-rebuild to ignore the problem, it doesn't fix it, but there's not
much more that you can do with binary-only packages, unfortunately, except
choose not to use them or buy hardware that requires them.  (Insert
standard gripe about slaveryware here, but it's your system, not mine, so
you get to choose what you run and I'd not deny you that right, regardless
of how much I gripe.)  

> Secondly openldap is referencing liblber 2.2 which is NOT present.
> 'equery f openldap' shows it is actually part of openldap, which I
> have rebuilt about 7 times to no avail.
> Actually the liblber files in openldap are 2.3 versions, not 2.2.
> libldap has both 2.2 and 2.3 versions, so I guess I'm running on 2.3,
> and the 2.2 are just there to cause me a headache. The installed
> version is 2.3.30-r2 so I don't know why it would contain 2.2 files.
>
> openldap is required by KDE multimedia, I'm not sure if I am actually
> exercising it.

Did you try rebuilding kdemultimedia, and/or anything else that might
require openldap?  Something's apparently still built against the old
version.  Either that or you have an orphan file that's built against the
old version that's still on your system for some reason, and need to find
and consider removing it.

BTW, if revdep-rebuild isn't providing you enough info about exactly what
it's finding and why, try running it with the --vv flag.  That's supposed
to make it extra verbose, and may provide further hints about what
it's finding that's causing it to want to rebuild whatever.  Then you can
use that to figure out what that's from.  -i is also useful, telling it to
ignore previous runs from the same day if you used --pretend on them, so
it doesn't use stale info if you've emerged stuff to fix it (or updated
the revdep config) by hand in the mean time.

BTW2, I'm a KDE guy myself but have (some of) the split packages merged,
not monolithic (as I think I mentioned before).  However, at least with
kde 3.5.6 (~arch), a pretend-merge of kde-meta doesn't grep up anything
ldap in either USE flags or packages, so either that dependency is gone in
newer KDE, or it's coming from an indirect dependency due to a USE flag
you have on that I have off.  You don't happen to have the the ldap USE
flag on, do you?  It doesn't sound like you'd be using it.  It's off here.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list