On Sun, 10 May 2009 03:58:41 +0300 Alexey Luchko <[email protected]> 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 ~ # > > > How to get it out? Try masking newer bash which blocks older portage, unmasking it after the newer portage is in place. If you have app-portage/gentoolkit installed, you can find out which specific versions of bash it depends on using the following command: equery depgraph --depth 1 portage | grep bash Otherwise you can use "portage --tree" or just look for DEPEND and RDEPEND vars in the ebuild itself, which can be found in /var/db/pkg. -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature
