When I try to emerge mailx, the ebuild failed when it tries to apply the patch multifix.diff.gz, but it seems the patch is correctly applied (see output below) Reproducible: Always Steps to Reproduce: 1. emerge mailx Actual Results: hostname root # emerge mailx Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/mailx-8.1.2.20021129-r2 to / >>> md5 src_uri ;-) mailx_8.1.1.orig.tar.gz >>> md5 src_uri ;-) multifix.diff.gz >>> md5 src_uri ;-) 20021129-cvs.diff.bz2 >>> Unpacking source... >>> Unpacking mailx_8.1.1.orig.tar.gz to /var/tmp/portage/mailx-8.1.2.20021129-r2/work >>> Unpacking multifix.diff.gz to /var/tmp/portage/mailx-8.1.2.20021129-r2/work >>> Unpacking 20021129-cvs.diff.bz2 to /var/tmp/portage/mailx-8.1.2.20021129-r2/work * Applying 20021129-cvs.diff.bz2... [ ok ] * Applying multifix.diff.gz... [ ok ] !!! ERROR: net-mail/mailx-8.1.2.20021129-r2 failed. !!! Function src_unpack, Line 31, Exitcode 1 !!! patch failed hostname root #
The offending line in the ebuild is: use ia64 && epatch ${FILESDIR}/mailx-64bit.diff || die "patch failed" It's better to use something like: if [ `use ia64` ] ; then epatch ${FILESDIR}/mailx-64bit.diff || die "patch failed" fi
this might work too: use ia64 && (epatch ${FILESDIR}/mailx-64bit.diff || die "patch failed")
use ia64 && (epatch ${FILESDIR}/mailx-64bit.diff || die "patch failed") will not stop the emerge process if the epatch command fails: * Applying mailx-64bit.diff... * Failed Patch: mailx-64bit.diff! * * Include in your bugreport the contents of: * * /var/tmp/portage/mailx-8.1.2.20021129-r2/temp/mailx-64bit.diff-3436.out !!! ERROR: net-mail/mailx-8.1.2.20021129-r2 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: mailx-64bit.diff! >>> Source unpacked. gcc -D_BSD_SOURCE -march=pentium4 -pipe -fomit-frame-pointer -c version.c ....
I'm new to bug submission, the proposition of Brandy Westcott resolve the problem, what i'm supposed to do ? Propose a patch, someone else will close the bug ? A patch will be submitted ? I want to thank you for your help Cordially
Additional Comment #1 also solved this problem for me. -r1 works fine too. Please add this modification into cvs.
Bug 29884 is a duplicate of this one due to my carelessness. Sorry.
*** Bug 29884 has been marked as a duplicate of this bug. ***
Fixed.
