public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Herber <herber@thing.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] a different revdep-rebuild problem and solution
Date: Fri, 29 Feb 2008 00:05:46 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802282342530.26122@thing.com> (raw)
In-Reply-To: <d257c3560802281215i28653707yf2a354001d1927ff@mail.gmail.com>

I had a slightly different revdep-rebuild problem and this discussion was
the impetus to uncover the cause.  The problem I had was that every time
I ran revdep-rebuild it wanted to rebuild a package that I had removed
and the package name was really weird.  At the end of the run it emitted
this command which I have reformatted for easy reading:

emerge --oneshot
 	=media-tv/-MERGING-mythtv-0.20_p11626
 	=media-tv/-MERGING-mythtv-0.20_p12172
 	=app-cdr/cdrkit-1.1.6
 	=media-libs/xine-lib-1.1.10.1

I didn't have any problem with the last two items, but I could not find
the weird -MERGING-mythtv packages.  I did remember having an emerge
problem with MythTV when I first started to try it.  After looking around
and not finding a likely suspect, I ran strace -f -o /tmp/revdep.out
revdep-rebuild.  After it hung I searched through all the open system
calls and finally found it checking out files in

 	/var/db/pkg/media-tv.

In the directory media-tv were subdirectories with the -MERGING name.
I removed all the directories in media-tv and reran revdep-rebuild and
all was well.

Thanks for the help!


Steve Herber	herber@thing.com		work: 206-221-7262
Security Engineer, UW Medicine, IT Services	home: 425-454-2399

On Thu, 28 Feb 2008, Beso wrote:

> 2008/2/28, manuel <kaos@manuelmarano.com>:
>>
>> Hi All,
>> I've ran revdep-rebuild a couple of times this week  and each  time i
>> run it it finds  a  broken link  referred  to  libqt-mt.so.3 and each
>> time It emerges
>> app-emulation/emul-linux-x86-soundlibs-2007112 to correct the problem!
>> but the broken link is still there!?? I can't fix it! any ideas?
>>
>> thanks in advance for your help
>>
>> Manuel
>
>
> log in a terminal as user, then  do a rm /root/.revdep* and then try again
> revdep-rebuild. after you do a revdep-rebuild be always sure that no .revdep
> files are present anymore in the /root/ directory. if there are some present
> then revdep will continue to cicle through them.
> another option would be to run revdep-rebuild -i (which stands for --ignore)
> which would ignore the .revdep files in the /root/ directory. i personally
> prefer the first option since i know that there aren't any cached revdeped
> files. if it continues to cycle on the same rebuild after one rebuild then
> it might be the case of a bug like the one of the gcj use flag in gcc-4.1.
> try searching on the forum if that might be the case.
>
>
>
> -- 
> dott. ing. beso
>
-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-29  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28  9:02 [gentoo-amd64] revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3 manuel
2008-02-28 19:02 ` [gentoo-amd64] " Duncan
2008-02-29 14:43   ` manuel
2008-02-28 20:15 ` [gentoo-amd64] " Beso
2008-02-29  8:05   ` Steve Herber [this message]
2008-02-29 12:34     ` [gentoo-amd64] Re: a different revdep-rebuild problem and solution Duncan
2008-02-29 16:46   ` [gentoo-amd64] revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3 Chris Brennan
2008-02-29 17:19     ` [gentoo-amd64] " Duncan
2008-02-29 17:24       ` Chris Brennan
2008-03-01  1:52         ` Duncan
2008-03-01  4:11           ` Chris Brennan
2008-03-01  9:08             ` Duncan
2008-03-01 10:10               ` Beso
2008-02-29 16:42 ` [gentoo-amd64] " David Fellows

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=Pine.LNX.4.64.0802282342530.26122@thing.com \
    --to=herber@thing.com \
    --cc=gentoo-amd64@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