Platform is SUSE Enterprise 10 SP2. Bootstrapping fails at the `emerge -e system' step; see below. This problem has been present since 2010-11-13. Strangely this version of tar was emerged successfully earlier (for example 2010-11-10). See also attached .patch.out file. >>> Emerging (91 of 138) app-arch/tar-1.23-r4 * tar-1.23.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * Package: app-arch/tar-1.23-r4 * Repository: gentoo_prefix * Maintainer: base-system@gentoo.org * USE: elibc_glibc kernel_linux nls prefix userland_GNU x86 >>> Unpacking source... >>> Unpacking tar-1.23.tar.bz2 to /local/scratch/portage/app-arch/tar-1.23-r4/work >>> Source unpacked in /local/scratch/portage/app-arch/tar-1.23-r4/work >>> Preparing source in /local/scratch/portage/app-arch/tar-1.23-r4/work/tar-1.23 ... * Applying tar-1.23-revert-pipe.patch ... [ ok ] * Applying tar-1.23-strncpy.patch ... [ ok ] * Applying tar-1.23-symlink-k-hang.patch ... [ ok ] * Applying tar-1.23-tests.patch ... [ ok ] * Applying rmt-prefix.patch ... * Failed Patch: rmt-prefix.patch ! * ( /local/scratch/nightly/2010-11-15/usr/portage/app-arch/tar/files/rmt-prefix.patch ) * * Include in your bugreport the contents of: * * /local/scratch/portage/app-arch/tar-1.23-r4/temp/rmt-prefix.patch.out
Created attachment 254371 [details] Filename says it all. File /local/scratch/portage/app-arch/tar-1.23-r4/temp/rmt-prefix.patch.out, containing one FAILED entry.
thanks, collateral damage with cleaning up of 1.25. Fixed this now.
Verified: Bootstrapping succeeds now.
