From: "Devon Miller" <devon.c.miller@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage: missing pieces
Date: Wed, 12 Jul 2006 13:02:58 -0400 [thread overview]
Message-ID: <c52221f0607121002m2393c399t691fcd8ab085599d@mail.gmail.com> (raw)
In-Reply-To: <7573e9640607060954j67ae48b0x4d1891d611d18b96@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
> >=sys-apps/shadow-4.0.14-r2 (is blocking sys-apps/pam-login-4.0.14)
The trick here is to unmerge pam-login, then merge shadow with USE="pam".
The functionality of pam-login has been folded into shadow, so using
pam-login is deprecated.
dcm
On 7/6/06, Richard Fish <bigfish@asmallpond.org> wrote:
>
> On 7/6/06, Molle Bestefich <molle.bestefich@gmail.com> wrote:
> >
> > ... snip ...
> >
> > Any other suggestions?
>
> Dont "snip". The relevant part comes *after* the "blocks" lines.
>
> Also, you are mis-interpreting the "blocks" lines. The correct
> reading of "X (is blocking Y)" is that you have (or should have) X
> installed, and now portage wants to install Y instead. Usually this
> is because Y supercedes the functionality that used to be provided by
> X, and in almost all cases, the right thing to do is to unmerge X and
> merge Y.
>
> The exceptions on your system are pam-login/shadow, and
> seamonkey/mozilla. For some reason portage wants to install/keep
> both. This is where you need to look at the *full* --tree output to
> see what is trying to pull those packages in.
>
> -Richard
> --
> gentoo-user@gentoo.org mailing list
>
>
[-- Attachment #2: Type: text/html, Size: 1705 bytes --]
prev parent reply other threads:[~2006-07-12 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 11:29 [gentoo-user] Portage: missing pieces Molle Bestefich
2006-06-21 12:09 ` Shaochun Wang
2006-06-21 13:07 ` Daniel da Veiga
2006-07-06 8:33 ` [gentoo-user] " Molle Bestefich
2006-07-06 8:44 ` Donnie Berkholz
2006-07-06 16:54 ` Richard Fish
2006-07-12 17:02 ` Devon Miller [this message]
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=c52221f0607121002m2393c399t691fcd8ab085599d@mail.gmail.com \
--to=devon.c.miller@gmail.com \
--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