Not sure what changed but this is the first night it failed in a long time. * Detected file collision(s): * * /home/user/gentoo/prefix-tinderbox-debian/long-dirname-on-purpose/a/b/etc/profile.d/00-gcc-paths.sh * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-devel/gcc-4.2.4-r01.2 * /home/user/gentoo/prefix-tinderbox-debian/long-dirname-on-purpose/a/b/etc/profile.d/00-gcc-paths.sh * * Package 'sys-devel/gcc-4.4.4-r1' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
(In reply to comment #0) > /home/user/gentoo/prefix-tinderbox-debian/long-dirname-on-purpose/a/b/etc/profile.d/00-gcc-paths.sh BTW, This means that CONFIG_PROTECT is broken. sys-apps/portage-2.2.01.16365
hmmm,very well possible
+# Jeremy Olexa <darkside@gentoo.org> (20 Sept 2010) +# Maybe an issue with CONFIG_PROTECT but definately and issue that impedes +# bootstrapping, mask until the next version comes out. bug 337945 +=sys-apps/portage-2.2.01.16365
should be fixed in git now: http://portage.prefix.freens.org/prefix/rev/ccac5591b590
portage-2.2.01.16610 released