Bugzilla Bug 215357

emerge -uv app-office/openoffice

These are the packages that would be merged, in order:

Calculating world dependencies... done!
[ebuild     U ] app-office/openoffice-2.4.0 [2.3.1-r1] USE="cups dbus firefox*
kde webdav -binfilter -debug -eds -gnome -gstreamer -gtk -java -ldap -mono -odk
-pam -seamonkey -xulrunner (-cairo%*) (-sound%)" LINGUAS="en_GB -af -ar -as_IN
-be_BY -bg -bn -br -bs -ca -cs -cy -da -de -dz -el -en -en_US -en_ZA -eo -es
-et -fa -fi -fr -ga -gl -gu_IN -he -hi_IN -hr -hu -it -ja -km -ko -ku -lt -lv
-mk -ml_IN -mr_IN -nb -ne -nl -nn -nr -ns -or_IN -pa_IN -pl -pt -pt_BR -ru -rw
-sh% -sk -sl -sr% -ss -st -sv -sw_TZ -ta_IN -te_IN -tg -th -ti_ER -tn -tr -ts
-uk -ur_IN -ve -vi -xh -zh_CN -zh_TW -zu (-sh_YU%) (-sr_CS%)" 229,282 kB

Total: 1 package (1 upgrade), Size of downloads: 229,282 kB
...

>>> Unpacking source...
>>> Unpacking ooo-build-2.4.0.5.tar.gz to /var/tmp/portage/app-office/openoffice-2.4.0/work
 * Applying gentoo-2.4.0.diff ...

 * Failed Patch: gentoo-2.4.0.diff !
 *  ( /usr/portage/app-office/openoffice/files/2.4.0/gentoo-2.4.0.diff )
 *
 * Include in your bugreport the contents of:
 *
 *  
/var/tmp/portage/app-office/openoffice-2.4.0/temp/gentoo-2.4.0.diff-245330.out

 *
 * ERROR: app-office/openoffice-2.4.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 5396:  Called epatch 'src_unpack'
 *             environment, line 2365:  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/tmp/portage/app-office/openoffice-2.4.0/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-office/openoffice-2.4.0/temp/environment'.
 *
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="." JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info

 * Messages for package app-office/openoffice-2.4.0:

 *
 *  It is important to note that OpenOffice.org is a very fragile
 *  build when it comes to CFLAGS.  A number of flags have already
 *  been filtered out.  If you experience difficulty merging this
 *  package and use agressive CFLAGS, lower the CFLAGS and try to
 *  merge again. Also note that building OOo takes a lot of time and
 *  hardware ressources: 4-6 GB free diskspace and 256 MB RAM are
 *  the minimum requirements. If you have less, use openoffice-bin
 *  instead.
 *
 *  You are building with java-support disabled, this results in some
 *  of the OpenOffice.org functionality (i.e. help) being disabled.
 *  If something you need does not work for you, rebuild with
 *  java in your USE-flags.
 *
 * Failed Patch: gentoo-2.4.0.diff !
 *  ( /usr/portage/app-office/openoffice/files/2.4.0/gentoo-2.4.0.diff )
 *
 * Include in your bugreport the contents of:
 *
 *  
/var/tmp/portage/app-office/openoffice-2.4.0/temp/gentoo-2.4.0.diff-245330.out
 *
 * ERROR: app-office/openoffice-2.4.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 5396:  Called epatch 'src_unpack'
 *             environment, line 2365:  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/tmp/portage/app-office/openoffice-2.4.0/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-office/openoffice-2.4.0/temp/environment'.
 *

Created an attachment (id=147644) [details]
emerge --info

Created an attachment (id=147646) [details]
build.log

Created an attachment (id=147648) [details]
Failed Patch: gentoo-2.4.0.diff

Created an attachment (id=147651) [details]
Environment

this has been fixed yesterday, please resync and try again

*** This bug has been marked as a duplicate of bug 215215 ***