| 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 |
| 37 |
>> |
| 38 |
>> |
| 39 |
> |
| 40 |
> |
| 41 |
> Only because I had to do this once myself. |
| 42 |
> |
| 43 |
> http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
| 44 |
|
| 45 |
From that link: |
| 46 |
|
| 47 |
"If your currently installed version of python reported by python -V |
| 48 |
is less than 2.6 then you must choose a version of portage that is |
| 49 |
compatible with it. If you have at least python 2.6 then use |
| 50 |
portage-2.1.10.41.tar.bz2. If you have python 2.4 or 2.5 then use |
| 51 |
portage-2.1.6.tar.bz2." |
| 52 |
|
| 53 |
I get: |
| 54 |
|
| 55 |
# python -V |
| 56 |
Python 2.5.2 |
| 57 |
|
| 58 |
and I'm already on portage-2.1.6.13 which is non-functional since it |
| 59 |
doesn't have high enough EAPI support for current ebuilds. |
| 60 |
|
| 61 |
I think I'm stuck between a python and portage upgrade. I can't |
| 62 |
update python with my current portage and I can't update portage with |
| 63 |
my current python. |
| 64 |
|
| 65 |
- Grant |
Archives