From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
Date: Thu, 24 Jan 2013 17:32:06 +0000 [thread overview]
Message-ID: <20130124173205.GA20483@acm.acm> (raw)
In-Reply-To: <20130124125116.GA20491@filip.loria.fr>
Hi, Jean-Christophe.
On Thu, Jan 24, 2013 at 01:51:16PM +0100, Jean-Christophe Bach wrote:
> * Alan Mackenzie <acm@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).
next prev parent reply other threads:[~2013-01-24 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 11:25 [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2 Alan Mackenzie
2013-01-24 12:51 ` Jean-Christophe Bach
2013-01-24 17:32 ` Alan Mackenzie [this message]
2013-01-24 13:02 ` Andrew Lowe
2013-01-24 13:10 ` Andrew Lowe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130124173205.GA20483@acm.acm \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox