public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
@ 2013-01-24 11:25 Alan Mackenzie
  2013-01-24 12:51 ` Jean-Christophe Bach
  2013-01-24 13:02 ` Andrew Lowe
  0 siblings, 2 replies; 5+ messages in thread
From: Alan Mackenzie @ 2013-01-24 11:25 UTC (permalink / raw
  To: gentoo-user

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).


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
  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
  2013-01-24 13:02 ` Andrew Lowe
  1 sibling, 1 reply; 5+ messages in thread
From: Jean-Christophe Bach @ 2013-01-24 12:51 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1799 bytes --]

* 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,

JC

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
  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 13:02 ` Andrew Lowe
  2013-01-24 13:10   ` Andrew Lowe
  1 sibling, 1 reply; 5+ messages in thread
From: Andrew Lowe @ 2013-01-24 13:02 UTC (permalink / raw
  To: gentoo-user

On 01/24/13 19:25, Alan Mackenzie wrote:
> 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% ]Same problem
>   *   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?
>

	Same problem here, although with V18.0-r1. I have 
net-libs/xulrunner-2.0.1-r1 on my machine, referring to 
Jean-Christophe's proposed fix. I'll kill this off with emerge -C and 
see what happens.

	Andrew


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
  2013-01-24 13:02 ` Andrew Lowe
@ 2013-01-24 13:10   ` Andrew Lowe
  0 siblings, 0 replies; 5+ messages in thread
From: Andrew Lowe @ 2013-01-24 13:10 UTC (permalink / raw
  To: gentoo-user

On 01/24/13 21:02, Andrew Lowe wrote:
> On 01/24/13 19:25, Alan Mackenzie wrote:
>> 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
[snip]
...
...
...
[snip]
>> Has anybody else encountered this problem, and what is the best way to
>> solve it?
>>
>
>      Same problem here, although with V18.0-r1. I have
> net-libs/xulrunner-2.0.1-r1 on my machine, referring to
> Jean-Christophe's proposed fix. I'll kill this off with emerge -C and
> see what happens.
>
>      Andrew

	Just killed off xulrunner and reran revdep-rebuild. This resulted in a 
clean run, nothing needed to be rebuilt. Firefox and Thunderbird both 
start up with no problems, so that seemed to be the fix.

	Andrew


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Infinite loop in revdep-rebuild with firefox-17.0.2
  2013-01-24 12:51 ` Jean-Christophe Bach
@ 2013-01-24 17:32   ` Alan Mackenzie
  0 siblings, 0 replies; 5+ messages in thread
From: Alan Mackenzie @ 2013-01-24 17:32 UTC (permalink / raw
  To: gentoo-user

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).


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-01-24 17:39 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2013-01-24 13:02 ` Andrew Lowe
2013-01-24 13:10   ` Andrew Lowe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox