On 1/10/10, Li <fender0107...@gmail.com> wrote:
> Hi all:
>
> I am trying emerge -e world, when the portage emerge coreutils, I got this
> massage:
>
>>>> Failed to emerge sys-apps/coreutils-7.5-r1, Log file:
>
>>>>  '/var/tmp/portage/sys-apps/coreutils-7.5-r1/temp/build.log'
>
> * Messages for package sys-apps/coreutils-7.5-r1:
>
> * Failed Patch: 001_all_coreutils-gen-progress-bar.patch !
> *  (
> *
> /var/tmp/portage/sys-apps/coreutils-7.5-r1/work/patch/001_all_coreutils-gen-progress-bar.patch
> *  )
> *
> * Include in your bugreport the contents of:
> *
> *
> /var/tmp/portage/sys-apps/coreutils-7.5-r1/temp/001_all_coreutils-gen-progress-bar.patch.out
> *
> * ERROR: sys-apps/coreutils-7.5-r1 failed.
> * Call stack:
> *               ebuild.sh, line   49:  Called src_unpack
> *             environment, line 2657:  Called epatch
> *             environment, line 1248:  Called die
> * The specific snippet of code:
> *               die "Failed Patch: ${patchname}!";
> *  The die message:
> *   Failed Patch:
> *   001_all_coreutils-gen-progress-bar.patch!
> *
> * If you need support, post the topmost build error,
> * and the call stack if relevant.
> * A complete build log is located at
> * '/var/tmp/portage/sys-apps/coreutils-7.5-r1/temp/build.log'.
> * The ebuild environment file is located at
> * '/var/tmp/portage/sys-apps/coreutils-7.5-r1/temp/environment'.
>
> system information:
>
>> uname -a
> Linux PC-686 2.6.31-gentoo-r6 #16 SMP PREEMPT Wed Jan 6 23:55:37 CST
> 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD
> GNU/Linux

Re-sync portage tree and try again.

eutils.eclass (where epatch is defined) has been changed several times
in the last 24 hours. The last change seems to fix something which
might be the direct cause of your problem (an EPATCH_EXCLUDES handling
bugfix, as according to the ebuild that 001_all_* patch is supposed to
be excluded?).

-- 
Arttu V.

Reply via email to