| 1 |
Roger Mason writes: |
| 2 |
|
| 3 |
> I'm building a system using a 2006.0 minimal install disk and |
| 4 |
> following the (current) installation docs. I got to the part where it |
| 5 |
> is suggested I upgrade portage. However, there is a blocker: |
| 6 |
> |
| 7 |
> (chroot) livecd / # emerge -p --oneshot portage |
| 8 |
> |
| 9 |
> These are the packages that would be merged, in order: |
| 10 |
> |
| 11 |
> Calculating dependencies... done! |
| 12 |
> |
| 13 |
> [ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17] |
| 14 |
> [ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5] |
| 15 |
> [ebuild U ] sys-apps/portage-2.1.4.4 [2.1.2.2] |
| 16 |
> *** Portage will stop merging at this point and reload itself, |
| 17 |
> then resume the merge. |
| 18 |
> [ebuild U ] app-shells/bash-3.2_p33 [3.1_p17] USE="-plugins%" |
| 19 |
> [blocks B ] <sys-apps/portage-2.1.4_rc1 (is blocking |
| 20 |
> app-shells/bash-3.2_p33) (chroot) livecd / # emerge -pC portage |
| 21 |
|
| 22 |
Waaaah! Better not. |
| 23 |
|
| 24 |
> >>> These are the packages that would be unmerged: |
| 25 |
> |
| 26 |
> !!! 'sys-apps/portage' is part of your system profile. |
| 27 |
> !!! Unmerging it may be damaging to your system. |
| 28 |
|
| 29 |
Right, you would be without portage, and "emerge portage" would not work. |
| 30 |
|
| 31 |
I'm not entirely sure what's going on, seems like the new portage needs a |
| 32 |
new bash, but your old portage will not work with this shell before |
| 33 |
upgrading, and the new bash will not work with the old portage. So you need |
| 34 |
to directly emerge a bash in-between. |
| 35 |
|
| 36 |
So, first try this: emerge -1a =app-shells/bash-3.2_p17-r1 |
| 37 |
You should be able to upgrade portage then fine: emerge -1a portage |
| 38 |
Then upgrade bash: emerge -ua bash (or emerge -ua world if you like) |
| 39 |
|
| 40 |
Wonko |
| 41 |
-- |
| 42 |
gentoo-user@l.g.o mailing list |
Archives