| 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 |
> What you need to do is upgrade portage incrementally, to increase your |
| 39 |
> available EAPI. |
| 40 |
> Versions available are ; |
| 41 |
> sys-apps/portage |
| 42 |
> Available versions: [M]2.1.6.7 2.1.6.13 2.1.10.11 2.1.10.41 (~)2.1.10.44 |
| 43 |
> |
| 44 |
> Try upgrading to 2.1.6.13 first, then 2.1.10.41 (perhaps with |
| 45 |
> intermediaries in between) |
| 46 |
|
| 47 |
I'm on 2.1.6.13 currently and I get EAPI errors when I try to emerge |
| 48 |
anything so I need a higher version. If I try for 2.1.10.11 I get: |
| 49 |
|
| 50 |
# emerge -av1 =portage-2.1.10.11 |
| 51 |
[snip] |
| 52 |
[ebuild NS ] dev-lang/python-2.7.2-r3 [2.5.2-r7] USE="gdbm ncurses |
| 53 |
readline ssl threads (wide-unicode) xml -berkdb -build -doc -examples |
| 54 |
-ipv6 -sqlite -tk -wininst" 11,494 kB |
| 55 |
[ebuild U ] sys-apps/portage-2.1.10.11 [2.1.6.13] USE="(ipc%*) |
| 56 |
less -build -doc -epydoc -python2% -python3% (-selinux)" LINGUAS="-pl" |
| 57 |
830 kB |
| 58 |
*** Portage will stop merging at this point and reload itself, |
| 59 |
then resume the merge. |
| 60 |
[blocks B ] dev-lang/python:2.7 ("dev-lang/python:2.7" is blocking |
| 61 |
sys-apps/portage-2.1.6.13) |
| 62 |
[blocks B ] <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is |
| 63 |
blocking dev-lang/python-2.7.2-r3) |
| 64 |
|
| 65 |
Total: 12 packages (5 upgrades, 6 new, 1 in new slot, 1 uninstall), |
| 66 |
Size of downloads: 16,070 kB |
| 67 |
Conflict: 3 blocks (2 unsatisfied) |
| 68 |
|
| 69 |
* Error: The above package list contains packages which cannot be |
| 70 |
* installed at the same time on the same system. |
| 71 |
|
| 72 |
('ebuild', '/', 'dev-lang/python-2.7.2-r3', 'merge') pulled in by |
| 73 |
dev-lang/python:2.7 required by ('ebuild', '/', |
| 74 |
'sys-apps/portage-2.1.10.11', 'merge') |
| 75 |
|
| 76 |
- Grant |
Archives