On 10 May 2009, at 01:58, Alexey Luchko wrote:
...
But then I've got the following collision. Obviously, a portage
update is required. But it is confused by dependencies:
colinux ~ # emerge portage --pretend --tree
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[nomerge ] sys-apps/portage-2.1.6.11 [2.1.2.2]
[ebuild U ] app-shells/bash-3.2_p39 [3.1_p17] USE="-examples% -
plugins%"
[ebuild U ] sys-apps/portage-2.1.6.11 [2.1.2.2]
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
[ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17]
[ebuild N ] app-arch/lzma-utils-4.32.7 USE="-nocxx"
[ebuild N ] app-admin/eselect-news-20080320
[ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE="-vim-
syntax%"
[ebuild U ] app-misc/pax-utils-0.1.19 [0.1.15]
[blocks B ] <sys-apps/portage-2.1.5 (is blocking app-shells/
bash-3.2_p39)
colinux ~ #
Hi there,
I have done some similar kinds of updates. Once stuff has been removed
from the tree it becomes a bit painful. I have had success, however,
reading the blocked ebuilds to find which versions of dependency
ebuilds are required, and then getting them from Gentoo's CVS "attic" <http://sources.gentoo.org/
>. You can place these in your local overlay and then `emerge
=category/package-version` to overcome the blocker.
This is probably a fair bit of work - one machine here is so old that
I accept I'll never get it updated (and a reinstall will be required,
when I get around to it), on another the work is not complete. On that
latter machine I have successfully updated some important packages to
the latest version (previously updated September 2007) by using this
method, but it required at least 2 or 3 blockers manually resolved
this way, and it did "feel" ugly. I suggest frequent use of `revdep-
rebuild`, `python-updater` and whatever else you can think of.
`emerge -pv --update world` on that machine still shows 202 packages
in need of updating, so this will need repeating a number of times.
I think a number of people here would tell you that this isn't
worthwhile, to back up /home directories & config files and to
reinstall, but personally I'm reluctant to do that in the case of a
working system on which users depend. So it _does_ appear possible to
upgrade using this tedious method.
In your case, I think you would first try to emerge =sys-apps/
portage-2.1.5, in order to unblock app-shells/bash-3.2_p39. This will
(surely) result in another blocker - resolve that first, then emerge
=sys-apps/portage-2.1.5 then try again to upgrade to the latest portage.
Good luck!
Stroller.
