| 1 |
> >=sys-apps/shadow-4.0.14-r2 (is blocking sys-apps/pam-login-4.0.14) |
| 2 |
The trick here is to unmerge pam-login, then merge shadow with USE="pam". |
| 3 |
The functionality of pam-login has been folded into shadow, so using |
| 4 |
pam-login is deprecated. |
| 5 |
|
| 6 |
dcm |
| 7 |
|
| 8 |
On 7/6/06, Richard Fish <bigfish@××××××××××.org> wrote: |
| 9 |
> |
| 10 |
> On 7/6/06, Molle Bestefich <molle.bestefich@×××××.com> wrote: |
| 11 |
> > |
| 12 |
> > ... snip ... |
| 13 |
> > |
| 14 |
> > Any other suggestions? |
| 15 |
> |
| 16 |
> Dont "snip". The relevant part comes *after* the "blocks" lines. |
| 17 |
> |
| 18 |
> Also, you are mis-interpreting the "blocks" lines. The correct |
| 19 |
> reading of "X (is blocking Y)" is that you have (or should have) X |
| 20 |
> installed, and now portage wants to install Y instead. Usually this |
| 21 |
> is because Y supercedes the functionality that used to be provided by |
| 22 |
> X, and in almost all cases, the right thing to do is to unmerge X and |
| 23 |
> merge Y. |
| 24 |
> |
| 25 |
> The exceptions on your system are pam-login/shadow, and |
| 26 |
> seamonkey/mozilla. For some reason portage wants to install/keep |
| 27 |
> both. This is where you need to look at the *full* --tree output to |
| 28 |
> see what is trying to pull those packages in. |
| 29 |
> |
| 30 |
> -Richard |
| 31 |
> -- |
| 32 |
> gentoo-user@g.o mailing list |
| 33 |
> |
| 34 |
> |
Archives