| 1 |
>>>> # emerge -avDuN system |
| 2 |
>>>> [snip] |
| 3 |
>>>> !!! All ebuilds that could satisfy ">=sys-auth/pambase-20081028" have |
| 4 |
>>>> been masked. |
| 5 |
>>>> !!! One of the following masked packages is required to complete your |
| 6 |
>>>> request: |
| 7 |
>>>> - sys-auth/pambase-20101024-r1 (masked by: EAPI 4) |
| 8 |
>>>> - sys-auth/pambase-20101024 (masked by: EAPI 3) |
| 9 |
>>> |
| 10 |
>>> |
| 11 |
>>> USE="-pam" emerge @system will avoid that particular block, although it |
| 12 |
>>> may only get you as far as the next one. |
| 13 |
>> |
| 14 |
>> |
| 15 |
>> I seem to get an error like this from whatever I try to emerge. Is |
| 16 |
>> untarring a stage3 my only option? |
| 17 |
>> |
| 18 |
>> - Grant |
| 19 |
>> |
| 20 |
> |
| 21 |
> You don't have to do the entire stage3 at once, |
| 22 |
> |
| 23 |
> http://tinderbox.dev.gentoo.org/ |
| 24 |
> |
| 25 |
> has precompiled packages for the major arches and profiles. You could try to |
| 26 |
> replace just pambase, pam, python, etc. -- whatever's giving you trouble. |
| 27 |
> |
| 28 |
> This was not my first recommendation because I've managed to break e.g. |
| 29 |
> `tar` and `cp` before in the attempt at which point you have two rescues to |
| 30 |
> attempt. |
| 31 |
|
| 32 |
The errors I'm getting seem to be complaining about emerging ebuilds |
| 33 |
with a higher EAPI number than my portage has. Should I just install |
| 34 |
the latest portage binary package? If so, how should I do that? |
| 35 |
|
| 36 |
- Grant |
Archives