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