Platform is SUSE10 Enterprise. Bootstrapping fails. There are detected file collisions when "Installing (26 of 27)", see summary of emerge activity at the end. The number of file collisions is large (239 to be exact). Many but not all are within portage, like: /local/tmp/h/usr/lib/portage/bin/chpathtool /local/tmp/h/usr/lib/portage/bin/archive-conf /local/tmp/h/usr/lib/portage/bin/check-implicit-pointer-usage.py I can put them all in an attachment if that helps. After the reported 239 collisions there is this, * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'sys-apps/portage-2.2.00.13346' merged despite file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * If you are an ebuild developer and you plan to commit ebuilds * with this system then please install dev-python/pycrypto or * enable the ssl USE flag for >=dev-lang/python-2.5 in order * to enable RMD160 hash support. * See bug #198398 for more information. * Byte compiling python modules for python-2.6 .. ... [ ok ] * * For help with using portage please consult the Gentoo Handbook * at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3 Finally the emerge of sys-apps/portage-2.2.00.13595 fails, again with package collisions: * package sys-apps/portage-2.2.00.13595 NOT merged * * Detected file collision(s): * * /local/tmp/h/usr/lib/portage/bin/Makefile * /local/tmp/h/usr/lib/portage/bin/Makefile.in * /local/tmp/h/usr/lib/portage/bin/banned-helper * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/die * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/eerror * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/einfo * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/eqawarn * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/ewarn * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/portageq * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/3/dodoc * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/3/dohard * /local/tmp/h/usr/lib/portage/bin/ebuild-helpers/3/dosed ---------------- Summary of emerge activity: /local/tmp> egrep -i 'emerging \(|emerge -' h/console.txt emerge --oneshot sed >>> Emerging (1 of 1) sys-apps/sed-4.1.5-r1 emerge --oneshot wget >>> Emerging (1 of 1) net-misc/wget-1.11.4 emerge --oneshot bash >>> Emerging (1 of 2) sys-libs/ncurses-5.7 >>> Emerging (2 of 2) app-shells/bash-3.2_p48-r1 emerge --oneshot --nodeps baselayout-prefix >>> Emerging (1 of 1) sys-apps/baselayout-prefix-1.12.5-r6 emerge --oneshot --nodeps lzma-utils >>> Emerging (1 of 1) app-arch/lzma-utils-4.32.7 emerge --oneshot --nodeps m4 >>> Emerging (1 of 1) sys-devel/m4-1.4.13 emerge --oneshot --nodeps flex >>> Emerging (1 of 1) sys-devel/flex-2.5.35 emerge --oneshot --nodeps bison >>> Emerging (1 of 1) sys-devel/bison-2.4.1 emerge --oneshot --nodeps binutils-config >>> Emerging (1 of 1) sys-devel/binutils-config-1.9-r04.14 emerge --oneshot --nodeps binutils >>> Emerging (1 of 1) sys-devel/binutils-2.19.51.0.3 emerge --oneshot --nodeps gcc-config >>> Emerging (1 of 1) sys-devel/gcc-config-1.4.1-r00.1 emerge --oneshot --nodeps "=gcc-4.2*" >>> Emerging (1 of 1) sys-devel/gcc-4.2.4-r1 emerge --oneshot coreutils >>> Emerging (1 of 1) sys-apps/coreutils-7.2 emerge --oneshot findutils >>> Emerging (1 of 1) sys-apps/findutils-4.5.2 emerge --oneshot tar >>> Emerging (1 of 1) app-arch/tar-1.22 emerge --oneshot grep >>> Emerging (1 of 1) sys-apps/grep-2.5.4-r1 emerge --oneshot patch >>> Emerging (1 of 1) sys-devel/patch-2.5.9-r1 emerge --oneshot gawk >>> Emerging (1 of 1) sys-apps/gawk-3.1.6 emerge --oneshot make >>> Emerging (1 of 1) sys-devel/make-3.81 emerge --oneshot --nodeps file >>> Emerging (1 of 1) sys-apps/file-5.00-r2 env FEATURES="-collision-protect" emerge --oneshot portage >>> Emerging (1 of 27) sys-devel/gnuconfig-20090203 >>> Emerging (2 of 27) app-misc/pax-utils-0.1.19 >>> Emerging (3 of 27) virtual/libiconv-0 >>> Emerging (4 of 27) sys-devel/automake-wrapper-3-r1 >>> Emerging (5 of 27) sys-devel/autoconf-wrapper-6-r00.1 >>> Emerging (6 of 27) sys-libs/zlib-1.2.3-r01.1 >>> Emerging (7 of 27) app-admin/eselect-1.0.11-r2 >>> Emerging (8 of 27) sys-libs/readline-5.2_p13 >>> Emerging (9 of 27) app-admin/eselect-news-20080320 >>> Emerging (10 of 27) app-admin/eselect-python-20080925 >>> Emerging (11 of 27) sys-devel/libperl-5.8.8-r2 >>> Emerging (12 of 27) dev-lang/perl-5.8.8-r5 >>> Emerging (13 of 27) app-admin/perl-cleaner-1.05 >>> Emerging (14 of 27) perl-core/Test-Harness-3.16 >>> Emerging (15 of 27) perl-core/PodParser-1.38 >>> Emerging (16 of 27) sys-apps/help2man-1.36.4 >>> Emerging (17 of 27) sys-apps/texinfo-4.13 >>> Emerging (18 of 27) sys-devel/autoconf-2.63-r1 >>> Emerging (19 of 27) sys-devel/automake-1.10.2-r00.1 >>> Emerging (20 of 27) sys-devel/libtool-2.2.6a >>> Emerging (21 of 27) sys-apps/sandbox-1.2.18.1-r3 >>> Emerging (22 of 27) dev-libs/popt-1.13 >>> Emerging (23 of 27) dev-libs/expat-2.0.1-r1 >>> Emerging (24 of 27) net-misc/rsync-3.0.5 >>> Emerging (25 of 27) dev-lang/python-2.6.1-r1 >>> Emerging (26 of 27) sys-apps/portage-2.2.00.13346 >>> Emerging (1 of 1) app-admin/python-updater-0.6-r1 emerge -u system >>> Emerging (1 of 31) sys-apps/portage-2.2.00.13595
% qlist sys-apps/portage | wc -l 272 chpathtool, archive-conf and check-implicit-pointer-usage.py are Portage provided files, so I still think it's a collision with Portage itself. Your second collision looks much more severe though (Makefile* ?!?)
i saw Makefile.in beeing installed by new portage too! CONTENTS excerpt: 88 obj /opt/gentoo/usr/lib/portage/bin/isolated-functions.sh 89 obj /opt/gentoo/usr/lib/portage/bin/Makefile 90 obj /opt/gentoo/usr/lib/portage/bin/Makefile.in 91 obj /opt/gentoo/usr/lib/portage/bin/md5check.py (md5 sums omitted for readability)
(In reply to comment #2) > i saw Makefile.in beeing installed by new portage too! CONTENTS excerpt: > related to recent build system changes... ?
I thought I updated the bootstrap-prefix.sh script to use a portage that no longer installs them (= latest version in the tree)
Just in case the full console log may be of interest, here is a link: http://wb748077.bahnhofbredband.se/diverse/console.txt.lzma
I've updated the snapshot, you should see no portage earlier than 2.2.00.13621
This morning there were no problems with the emerging of portage. The command env FEATURES="-collision-protect" emerge --oneshot portage pulls in 27 packages, and number 26 of those is portage-2.2.00.13621. Bootstrapping fails further on, probably unrelated, I will report this separately.
For the record, the "further on" problem is http://bugs.gentoo.org/show_bug.cgi?id=269484.
ok, probably a perl thing. I'm closing this one then.
