| 1 |
On Sun, 10 May 2009 03:58:41 +0300 |
| 2 |
Alexey Luchko <luchik@×××××.com> wrote: |
| 3 |
|
| 4 |
> But then I've got the following collision. Obviously, a portage update |
| 5 |
> is required. But it is confused by dependencies: |
| 6 |
> colinux ~ # emerge portage --pretend --tree |
| 7 |
> |
| 8 |
> These are the packages that would be merged, in reverse order: |
| 9 |
> |
| 10 |
> Calculating dependencies... done! |
| 11 |
> [nomerge ] sys-apps/portage-2.1.6.11 [2.1.2.2] |
| 12 |
> [ebuild U ] app-shells/bash-3.2_p39 [3.1_p17] USE="-examples% - |
| 13 |
> plugins%" |
| 14 |
> [ebuild U ] sys-apps/portage-2.1.6.11 [2.1.2.2] |
| 15 |
> [ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5] |
| 16 |
> [ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17] |
| 17 |
> [ebuild N ] app-arch/lzma-utils-4.32.7 USE="-nocxx" |
| 18 |
> [ebuild N ] app-admin/eselect-news-20080320 |
| 19 |
> [ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE="-vim-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 |
> |
| 26 |
> How to get it out? |
| 27 |
|
| 28 |
Try masking newer bash which blocks older portage, unmasking it after |
| 29 |
the newer portage is in place. |
| 30 |
|
| 31 |
If you have app-portage/gentoolkit installed, you can find out which |
| 32 |
specific versions of bash it depends on using the following command: |
| 33 |
|
| 34 |
equery depgraph --depth 1 portage | grep bash |
| 35 |
|
| 36 |
Otherwise you can use "portage --tree" or just look for DEPEND and |
| 37 |
RDEPEND vars in the ebuild itself, which can be found in /var/db/pkg. |
| 38 |
|
| 39 |
-- |
| 40 |
Mike Kazantsev // fraggod.net |
Archives