Hi, Jean-Christophe. On Thu, Jan 24, 2013 at 01:51:16PM +0100, Jean-Christophe Bach wrote: > * Alan Mackenzie <a...@muc.de> [24.01.2013. @11:25:45 +0000]:
> > Hi, Gentoo! > > A couple of days ago, I merged firefox-17.0.2 and ran revdep-rebuild -p. > > It said, strangely, that some firefox libraries needed rebuilding. > > I've just let revdep-rebuild rebuild firefox. I run revdep-rebuild -p > > again, and it's still saying these libraries need rebuilding. This > > isn't good. > > Here's some output from revdep-rebuild -p: > > * Checking dynamic linking consistency > > [ 100% ] > > * broken /usr/lib64/firefox/libxpcom.so (no version information > > available) > > * broken /usr/lib64/firefox/plugin-container (no version information > > available) > > * broken /usr/lib64/firefox/sdk/bin/xpcshell (no version information > > available) > > * broken /usr/lib64/firefox/sdk/lib/libxpcom.so (no version information > > available) > > * Generated new 3_broken.rr > > * Assigning files to packages > > * /usr/lib64/firefox/libxpcom.so -> www-client/firefox > > * /usr/lib64/firefox/plugin-container -> www-client/firefox > > * /usr/lib64/firefox/sdk/bin/xpcshell -> www-client/firefox > > * /usr/lib64/firefox/sdk/lib/libxpcom.so -> www-client/firefox > > The problem seems to be the "no version information available". > > revdep-rebuild is now less useful than it should be. > > Has anybody else encountered this problem, and what is the best way to > > solve it? > > -- > > Alan Mackenzie (Nuremberg, Germany). > Hi, > I also had this problem: it was due to the fact I had an old version of > xulrunner installed on my computer. > To address the problem, I only removed xulrunner : > rm -Rf /usr/lib/xulrunner-* > But I think that it would have been better to clean it by using : > emerge -aC xulrunner > Hope it will solve your infinite revdep-rebuild loop, Yes, indeed it did, thanks. Although I had xulrunner hanging around, there was no longer an ebuild for it. > JC -- Alan Mackenzie (Nuremberg, Germany).
