revdep-rebuild: broken libtool files -- is portage leaking?

Message

the_bat · Post by **the_bat** » Wed Oct 03, 2007 7:31 pm

Hi,

running revdep-rebuild gives me many lines of:

Checking dynamic linking consistency...
  broken /usr/lib/graphviz/libgv_perl.la (requires /usr/lib/graphviz/libgvc.la)
  broken /usr/lib/graphviz/libgv_perl.la (requires /usr/lib/graphviz/libgraph.la)
  broken /usr/lib/graphviz/libgv_perl.la (requires /usr/lib/graphviz/libcdt.la)
  broken /usr/lib/graphviz/libgv_perl.la (requires /usr/lib/graphviz/libpathplan.la)
  broken /usr/lib/graphviz/libgv_perl.la (requires /usr/lib/graphviz/libgvgd.la)
  broken /usr/lib/graphviz/libgv_python.la (requires /usr/lib/graphviz/libgvc.la)
  broken /usr/lib/graphviz/libgv_python.la (requires /usr/lib/graphviz/libgraph.la)
  broken /usr/lib/graphviz/libgv_python.la (requires /usr/lib/graphviz/libcdt.la)
  broken /usr/lib/graphviz/libgv_python.la (requires /usr/lib/graphviz/libpathplan.la)
  broken /usr/lib/graphviz/libgv_python.la (requires /usr/lib/graphviz/libgvgd.la)
  broken /usr/lib/graphviz/libgv_ruby.la (requires /usr/lib/graphviz/libgvc.la)
...
  broken /usr/lib/libsigc-1.2.la (requires /-lstdc++)
  broken /usr/lib/xmms/Input/libxmms-flac.la (requires /usr/lib/libxmms.la)
  broken /usr/lib/xmms/Input/libxmmssid.la (requires /usr/lib/libxmms.la)
  broken /usr/lib/xmms/Input/libxmmssid.la (requires /usr/lib/libsidplay.la)
 done.
  (/root/.revdep-rebuild.3_rebuild)

I tried to determine the owner for some of these files with

Code: Select all

equery belongs ...

.
but they do not belong to any installed package.

Now my question: why are these files still on my system? They where probably lost on unmerging old packages?

Can I savely remove them? Is there an automatic way to do so (excecp for "grep | xargs rm")?

Is this a bug in the package management system?

Cheers,
Martin

Vitaliy · Post by **Vitaliy** » Wed Oct 03, 2007 7:38 pm

Run revdep-rebuild to make sure everything is intact, and then run emerge --depclean to remove unnecessary packages/dependencies. See if you have the issue after that.

the_bat · Post by **the_bat** » Wed Oct 03, 2007 8:04 pm

Thanks for your answer, but ...

Run revdep-rebuild to make sure everything is intact,

I have done this (also many times before).

run emerge --depclean to remove unnecessary packages/dependencies

I have also done this (also many times before).

See if you have the issue after that.

I'm not having "issues". I just think that maybe portage does "leak" some files.

Does anyone else see such .la files without a package owning them?

Cheers,
Martin

AllenJB · Post by **AllenJB** » Wed Oct 03, 2007 10:07 pm

Run "rm -rf ~/.revdep*" - this will remove the files that revdep-rebuild uses to cache its information and make sure you're using an up-to-date set of data.

swimmer · Post by **swimmer** » Wed Oct 03, 2007 10:15 pm

the_bat: after looking up carefully that those files are really cruft it is normally safe to remove them ... I do that many times - given the fact I check thoroughly!!!

Otherwise you should be able to fix it by re-emerging the troublemakers anyway ...

HTH
swimmer

the_bat · Post by **the_bat** » Thu Oct 04, 2007 8:08 am

Doing this:

Code: Select all

"rm -rf ~/.revdep*"

will not change that I have files in my system (*.la files) that belong to no package. This is the problem here.

revdep-rebuild just made me aware of these files. I do not have a problem using revdep-rebuild.

@swimmer: So you are saying you also have left-over files from removed packages from time to time? This would actually mean that portage is leaking files, right?

If someone could confirm this, maybe a bug should be filed?

after looking up carefully that those files are really cruft

How exactly would I determine that nothing on my system relies on those anymore?

Cheers,
Martin

swimmer · Post by **swimmer** » Thu Oct 04, 2007 10:43 am

the_bat wrote:[...]
@swimmer: So you are saying you also have left-over files from removed packages from time to time? This would actually mean that portage is leaking files, right?

If someone could confirm this, maybe a bug should be filed?

after looking up carefully that those files are really cruft
How exactly would I determine that nothing on my system relies on those anymore?

Cheers,
Martin

Yes - I hereby confirm that I have left-over files from removed packages.

My most reliable tool for checking is 'equery b' - if this reports that the files do not belong to any package I dare to remove them

Greetz
swimmer