From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] infinite battle between emerge --depclean and revdep-rebuild
Date: Fri, 14 Jul 2006 08:05:37 -0400 [thread overview]
Message-ID: <yu97j2gpf1q.fsf@nyu.edu> (raw)
In-Reply-To: <7573e9640607140142n5167d6f1mcacd4a0dd0709a2b@mail.gmail.com> (Richard Fish's message of "Fri, 14 Jul 2006 01:42:26 -0700")
At Fri, 14 Jul 2006 01:42:26 -0700 Richard Fish <bigfish@asmallpond.org> wrote:
> On 7/13/06, Allan Gottlieb <gottlieb@nyu.edu> wrote:
>> ajglap gottlieb # emerge --ask --depclean; revdep-rebuild --pretend
>
> Looks like a circular dependancy between gst-plugins-alsa and
> gst-plugins. Circular dependancies are not handled well in portage.
>
>> *** WARNING *** --depclean is known to be broken. It is highly recommended
>> [rest of warning snipped]
>
> Did you read the rest of the warning??? It gives you the solution:
>
> emerge --noreplace gst-plugins
I did read it, but obviously not with full understanding. That
solution, which indeed does solve my problem, is correctly stated to
place gst-plugins into the world file. But that is not what I though
world was for. I though it was for applications that I use directly.
I thought the --noreplace suggestion was for the case when --depclean
wants to remove something you actually run. I foolishly hadn't
realized that this advice emerge --noreplace <atom> was also to be
used to break circular dependencies.
Thanks for the enlightenment.
allan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-14 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 4:30 [gentoo-user] infinite battle between emerge --depclean and revdep-rebuild Allan Gottlieb
2006-07-14 8:42 ` Richard Fish
2006-07-14 11:25 ` Janusz Bossy
2006-07-14 16:27 ` Richard Fish
2006-07-14 12:05 ` Allan Gottlieb [this message]
2006-07-14 16:29 ` Richard Fish
2006-07-18 20:53 ` [gentoo-user] " Francesco Talamona
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=yu97j2gpf1q.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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