Summary: | sys-apps/portage-2.1.6.7 - ebuild tries to re-apply patches in src_prepare when src_prepare has already been run | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | loki_val |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 261959 |
Description
Pacho Ramos
2009-03-14 12:46:18 UTC
I can't reproduce with portage-2.2_rc24 Can you try to reproduce with: ebuild $ebuild clean prepare ebuild $ebuild install pa@loki ~/Desktop/Downloads $ ebuild /usr/portage/dev-lang/mono/mono-2.2-r3.ebuild clean prepare * mono-2.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking mono-2.2.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking mono-2.2.tar.bz2 to /var/tmp/portage/dev-lang/mono-2.2-r3/work >>> Source unpacked in /var/tmp/portage/dev-lang/mono-2.2-r3/work >>> Preparing source in /var/tmp/portage/dev-lang/mono-2.2-r3/work/mono-2.2 ... * Applying mono-2.2-libdir126.patch ... [ ok ] * Applying mono-2.2-ppc-threading.patch ... [ ok ] * Applying mono-2.2-uselibdir.patch ... [ ok ] * Applying mono-2.2-r121596-work-around-runtime-crash.patch ... [ ok ] * Applying mono-2.2-r123987-bless-crash.patch ... [ ok ] >>> Source prepared. pa@loki ~/Desktop/Downloads $ ebuild /usr/portage/dev-lang/mono/mono-2.2-r3.ebuild install >>> Existing ${T}/environment for 'mono-2.2-r3' will be sourced. Run >>> 'clean' to start with a fresh environment. * mono-2.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking mono-2.2.tar.bz2 ;-) ... [ ok ] >>> Checking mono-2.2.tar.bz2's mtime... >>> WORKDIR is up-to-date, keeping... >>> It appears that 'mono-2.2-r3' is already prepared; skipping. >>> Remove '/var/tmp/portage/dev-lang/mono-2.2-r3/.prepared' to force prepare. >>> Configuring source in /var/tmp/portage/dev-lang/mono-2.2-r3/work/mono-2.2 ... * econf: updating mono-2.2/libgc/config.guess with /usr/share/gnuconfig/config.guess * econf: updating mono-2.2/libgc/config.sub with /usr/share/gnuconfig/config.sub * econf: updating mono-2.2/config.guess with /usr/share/gnuconfig/config.guess * econf: updating mono-2.2/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-dependency-tracking --disable-static --disable-quiet-build --with-preview --with-glib=system --with-moonlight --with-libgdiplus=installed --without-xen_opt --without-ikvm-native --with-jit Fails here with current stable portage: # ebuild mono-2.2-r3.ebuild clean prepare * mono-2.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking mono-2.2.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking mono-2.2.tar.bz2 to /var/tmp/portage/dev-lang/mono-2.2-r3/work >>> Source unpacked in /var/tmp/portage/dev-lang/mono-2.2-r3/work * Applying mono-2.2-libdir126.patch ... [ ok ] * Applying mono-2.2-ppc-threading.patch ... [ ok ] * Applying mono-2.2-uselibdir.patch ... [ ok ] * Applying mono-2.2-r121596-work-around-runtime-crash.patch ... [ ok ] * Applying mono-2.2-r123987-bless-crash.patch ... [ ok ] belkin3 mono # ebuild mono-2.2-r3.ebuild install >>> Existing ${T}/environment for 'mono-2.2-r3' will be sourced. Run >>> 'clean' to start with a fresh environment. * mono-2.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking mono-2.2.tar.bz2 ;-) ... [ ok ] >>> Checking mono-2.2.tar.bz2's mtime... >>> WORKDIR is up-to-date, keeping... * Applying mono-2.2-libdir126.patch ... * Failed Patch: mono-2.2-libdir126.patch ! * ( /var/tmp/portage/dev-lang/mono-2.2-r3/work/mono-2.2-libdir126.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-lang/mono-2.2-r3/temp/mono-2.2-libdir126.patch-21941.out * * ERROR: dev-lang/mono-2.2-r3 failed. * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 3092: Called go-mono_src_prepare * environment, line 2160: Called base_src_util 'autopatch' * environment, line 531: Called epatch '/var/tmp/portage/dev-lang/mono-2.2-r3/work/mono-2.2-libdir126.patch' * environment, line 1561: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: mono-2.2-libdir126.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/dev-lang/mono-2.2-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/mono-2.2-r3/temp/environment'. * Could someone try portage-2.1.6.8 and see if that has a fix for this? This should be fixed in 2.1.6.8 and 2.2_rc24: http://sources.gentoo.org/viewcvs.py/portage?rev=12795&view=rev Great :-D |