On Mon, Sep 19, 2011 at 10:20 AM, Allan Gottlieb <[email protected]> wrote: > On Mon, Sep 19 2011, Alan McKinnon wrote: >>> > revdep-rebuild checks everything, revdep-rebuild --library >>> > checks just some things. >>> > >>> > ebuilds sometimes issue messages to check just the libraries known >>> > to have been updated, but a full revdep-rebuild after an update >>> > will catch those anyway. >>> >>> Until recently I skipped the "--library" step exactly because I knew >>> revdep-rebuild will find and fix the broken packages after I delete >>> the old library. So, why bother with the --library step, right? >>> >>> However. A few weeks ago I got caught when I deleted one of those >>> obsolete libraries and only then did I find out that gcc is one of >>> the packages that depend on it :( >>> >>> I don't skip the --library step any more. >> >> That's odd behaviour, I wonder what caused the difference. >> >> Surely revdep-rebuild itself can't do this different just because you >> specified a library to compare? I wonder if that lib was maybe in the >> revdep-rebuild exclude list. >> >> I'd be interested to track it down for reference, do you remember the >> library involved? > > It occurs exactly in the case we are discussing libpng > > ajglap gottlieb # revdep-rebuild; revdep-rebuild --library > '/usr/lib64/libpng14.so.14' > * Configuring search environment for revdep-rebuild > > * Checking reverse dependencies > * Packages containing binaries and libraries broken by a package update > * will be emerged. > > * Collecting system binaries and libraries > * Generated new 1_files.rr > * Collecting complete LD_LIBRARY_PATH > * Generated new 2_ldpath.rr > * Checking dynamic linking consistency > [ 100% ] > > * Dynamic linking on your system is consistent... All done. > * Configuring search environment for revdep-rebuild > > * Checking reverse dependencies > * Packages containing binaries and libraries using /usr/lib64/libpng14.so.14 > * will be emerged. > > * Collecting system binaries and libraries > * Generated new 1_files.rr > * Checking dynamic linking > [ 8% ] * found /usr/bin/dia > [ 46% ] * found /usr/lib64/dia/libaadl_objects.so > * found /usr/lib64/dia/libart_filter.so > * found /usr/lib64/dia/libcairo_filter.so > * found /usr/lib64/dia/libcgm_filter.so > * found /usr/lib64/dia/libchronogram_objects.so > * found /usr/lib64/dia/libcustom_lines_objects.so > * found /usr/lib64/dia/libcustom_objects.so > * found /usr/lib64/dia/libdb_objects.so > * found /usr/lib64/dia/libdia.so > * found /usr/lib64/dia/libdxf_filter.so > * found /usr/lib64/dia/liber_objects.so > * found /usr/lib64/dia/libflowchart_objects.so > * found /usr/lib64/dia/libfs_objects.so > * found /usr/lib64/dia/libgrafcet_objects.so > * found /usr/lib64/dia/libhpgl_filter.so > * found /usr/lib64/dia/libistar_objects.so > * found /usr/lib64/dia/libjackson_objects.so > * found /usr/lib64/dia/libkaos_objects.so > * found /usr/lib64/dia/libmetapost_filter.so > * found /usr/lib64/dia/libmisc_objects.so > * found /usr/lib64/dia/libnetwork_objects.so > * found /usr/lib64/dia/libpgf_filter.so > * found /usr/lib64/dia/libpixbuf_filter.so > * found /usr/lib64/dia/libpostscript_filter.so > * found /usr/lib64/dia/libpstricks_filter.so > * found /usr/lib64/dia/libpython_plugin.so > ^C * ...terminated. Removing incomplete 3_broken.rr 3_errors.rr.
Is there no automated way to catch these? --library expects an argument; how do I know which libraries to feed it? -- :wq
