sys-apps/coreutils-7.4 ebuild tries to patch the source with coreutils-7.2-mgetgroups-darwin.patch, which fails. The source already includes the changes in the patch, so the call to epatch should probably be removed.
Probably hit by the same issue when bootstrapping on SUSE 10 Enteprise: >>> Unpacking coreutils-7.4-patches-1.tar.lzma to /local/scratch/portage/sys-apps/coreutils-7.4/work ACCESS DENIED open_wr: /var/opt/quest/vas/vasd/vas_misc.vdb ACCESS DENIED open_wr: /var/opt/quest/vas/vasd/vas_ident.vdb >>> Unpacking coreutils-7.4.tar.gz to /local/scratch/portage/sys-apps/coreutils-7.4/work * Applying various patches (bugfixes/updates) ... * 003_all_coreutils-gentoo-uname.patch ... [ ok ] * 010_all_coreutils-tests.patch ... [ ok ] * 015_all_coreutils-mv-i-3-stdin.patch ... [ ok ] * 030_all_coreutils-more-dir-colors.patch ... [ ok ] * Done with patching * Applying coreutils-7.2-mgetgroups-darwin.patch ... * Failed Patch: coreutils-7.2-mgetgroups-darwin.patch ! * ( /local/scratch/nightly/2009-05-12/usr/portage/sys-apps/coreutils/files/coreutils-7.2-mgetgroups-darwin.patch ) * * Include in your bugreport the contents of: * * /local/scratch/portage/sys-apps/coreutils-7.4/temp/coreutils-7.2-mgetgroups-darwin.patch-1862.out * ERROR: sys-apps/coreutils-7.4 failed: * Failed Patch: coreutils-7.2-mgetgroups-darwin.patch!
Patch was applied upstream, so patch removed. Thanks!
The problem still occurs, though earlier on in the bootstrapping. Here is a summary of the emerge operations carried out; the last one fails. >>> Emerging (1 of 1) sys-apps/sed-4.1.5-r1 >>> Emerging (1 of 1) net-misc/wget-1.11.4 >>> Emerging (1 of 2) sys-libs/ncurses-5.7 >>> Emerging (2 of 2) app-shells/bash-4.0_p17-r1 >>> Emerging (1 of 1) sys-apps/baselayout-prefix-1.12.5-r6 >>> Emerging (1 of 1) app-arch/lzma-utils-4.32.7 >>> Emerging (1 of 1) sys-devel/m4-1.4.13 >>> Emerging (1 of 1) sys-devel/flex-2.5.35 >>> Emerging (1 of 1) sys-devel/bison-2.4.1 >>> Emerging (1 of 1) sys-devel/binutils-config-1.9-r04.14 >>> Emerging (1 of 1) sys-devel/binutils-2.19.51.0.4 >>> Emerging (1 of 1) sys-devel/gcc-config-1.4.1-r00.2 >>> Emerging (1 of 1) sys-devel/gcc-4.2.4-r1 >>> Emerging (1 of 1) sys-apps/coreutils-7.4 Snippet from the console log of the last emerge: >>> Unpacking coreutils-7.4-patches-1.tar.lzma to /local/scratch/portage/sys-apps/coreutils-7.4/work >>> Unpacking coreutils-7.4.tar.gz to /local/scratch/portage/sys-apps/coreutils-7.4/work * Applying various patches (bugfixes/updates) ... * 003_all_coreutils-gentoo-uname.patch ... [ ok ] * 010_all_coreutils-tests.patch ... [ ok ] * 015_all_coreutils-mv-i-3-stdin.patch ... [ ok ] * 030_all_coreutils-more-dir-colors.patch ... [ ok ] * Done with patching * Applying coreutils-7.2-mgetgroups-darwin.patch ... * Failed Patch: coreutils-7.2-mgetgroups-darwin.patch ! * ( /local/scratch/nightly/2009-05-13/usr/portage/sys-apps/coreutils/files/coreutils-7.2-mgetgroups-darwin.patch ) * * Include in your bugreport the contents of: * * /local/scratch/portage/sys-apps/coreutils-7.4/temp/coreutils-7.2-mgetgroups-darwin.patch-19615.out * ERROR: sys-apps/coreutils-7.4 failed: * Failed Patch: coreutils-7.2-mgetgroups-darwin.patch!
Indeed right, as only today I could update the bootstrap snapshot, which I just did. Tomorrow should be fine again then.
Confirming: Successful bootstrapping this morning.
great, thanks!
