Bug 215215 - app-office/openoffice-2.4.0 fails with a bad patch.
|
Bug#:
215215
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: openoffice@gentoo.org
|
Reported By: zeekec@mad.scientist.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: app-office/openoffice-2.4.0 fails with a bad patch.
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-03-28 15:56 0000
|
The configure.in portion of the gentoo-2.4.0.diff is no longer valid (I don't
know if it's still needed or not.).
>>> Unpacking source...
>>> Unpacking ooo-build-2.4.0.5.tar.gz to /gentoo/tmp/portage/app-office/openoffice-2.4.0/work
* Applying gentoo-2.4.0.diff ...
* Failed Patch: gentoo-2.4.0.diff !
* ( /gentoo/portage/app-office/openoffice/files/2.4.0/gentoo-2.4.0.diff )
*
* Include in your bugreport the contents of:
*
*
/gentoo/tmp/portage/app-office/openoffice-2.4.0/temp/gentoo-2.4.0.diff-16549.out
*
* ERROR: app-office/openoffice-2.4.0 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 5419: Called epatch 'src_unpack'
* environment, line 2388: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
* The die message:
* Failed Patch: gentoo-2.4.0.diff!
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located at
'/var/log/portage/app-office:openoffice-2.4.0:20080328-153535.log'.
* The ebuild environment file is located at
'/gentoo/tmp/portage/app-office/openoffice-2.4.0/temp/environment'.
*
!!! When you file a bug report, please include the following information:
GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.05"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
and of course, the output of emerge --info
It seems that configure.in does not need to be patched. In my case, unpatched
line 1080 is as follows:
elif test "$with_tag" = "OOH680_m12" ; then
and not as this:
elif test "$with_tag" = "OOH680_m11" ; then
After removing the configure.in section from the patch, it applies well.
Yeah, stupid mistake, forgot to update the patch...
Thanks for reporting, should be fixed now
*** Bug 215357 has been marked as a duplicate of this bug. ***