Roger Mason writes:
> I'm building a system using a 2006.0 minimal install disk and
> following the (current) installation docs. I got to the part where it
> is suggested I upgrade portage. However, there is a blocker:
>
> (chroot) livecd / # emerge -p --oneshot portage
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> [ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17]
> [ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
> [ebuild U ] sys-apps/portage-2.1.4.4 [2.1.2.2]
> *** Portage will stop merging at this point and reload itself,
> then resume the merge.
> [ebuild U ] app-shells/bash-3.2_p33 [3.1_p17] USE="-plugins%"
> [blocks B ] <sys-apps/portage-2.1.4_rc1 (is blocking
> app-shells/bash-3.2_p33) (chroot) livecd / # emerge -pC portage
Waaaah! Better not.
> >>> These are the packages that would be unmerged:
>
> !!! 'sys-apps/portage' is part of your system profile.
> !!! Unmerging it may be damaging to your system.
Right, you would be without portage, and "emerge portage" would not work.
I'm not entirely sure what's going on, seems like the new portage needs a
new bash, but your old portage will not work with this shell before
upgrading, and the new bash will not work with the old portage. So you need
to directly emerge a bash in-between.
So, first try this: emerge -1a =app-shells/bash-3.2_p17-r1
You should be able to upgrade portage then fine: emerge -1a portage
Then upgrade bash: emerge -ua bash (or emerge -ua world if you like)
Wonko
--
gentoo-user@lists.gentoo.org mailing list
