There is something wrong with the tarball although the package can be (re)installed. emerge --complete-graph=y --oneshot app-office/libreoffice-bin:0 .......... Calculating dependencies... done! >>> Verifying ebuild manifests >>> Running pre-merge checks for app-office/libreoffice-bin-3.4.3.2-r1 >>> Emerging (1 of 1) app-office/libreoffice-bin-3.4.3.2-r1 * libreoffice-base-java-x86-3.4.3.2-r1.tbz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking libreoffice-base-java-x86-3.4.3.2-r1.tbz2 to /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/work bzip2: /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/distdir/libreoffice-base-java-x86-3.4.3.2-r1.tbz2: trailing garbage after EOF ignored >>> Source unpacked in /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/work >>> Preparing source in /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/work ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/work ... >>> Source compiled. >>> Test phase [not enabled]: app-office/libreoffice-bin-3.4.3.2-r1 >>> Install libreoffice-bin-3.4.3.2-r1 into /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/image/ category app-office >>> Completed installing libreoffice-bin-3.4.3.2-r1 into /var/tmp/portage/app-office/libreoffice-bin-3.4.3.2-r1/image/ ecompressdir: bzip2 -9 /usr/share/man >>> Installing (1 of 1) app-office/libreoffice-bin-3.4.3.2-r1 * Updating icons cache ... [ ok ] * Updating desktop mime database ... * Updating shared mime info database ... * Updating icons cache ... [ ok ] * Updating desktop mime database ... * Updating shared mime info database ... * PT PaX marking -m * /usr/lib/libreoffice/program/soffice.bin * Messages for package app-office/libreoffice-bin-3.4.3.2-r1: * PT PaX marking -m * /usr/lib/libreoffice/program/soffice.bin >>> Auto-cleaning packages...
Should be no problem at all. It's a Gentoo style tbz2 so it has some metadata tagged on to the end that bzip2 does not (need to) understand.
As the Jeroen said, it is some metadata stuff that is included in gentoo binpkgs. Nothing we can do about it. Also it is quite harmless :)
