Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 379655

Summary: app-office/libreoffice-bin-3.3.4 fails to unpack
Product: Gentoo Linux Reporter: Denilson Sá Maia <denilsonsa>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Denilson Sá Maia 2011-08-18 06:14:22 UTC
app-office/libreoffice-bin-3.3.4 is now available and marked as stable (this is why I've increased the priority of this bug). However, it fails to unpack:


>>> Unpacking ./LibO_3.3.4rc2_Linux_x86-64_install-rpm_en-US/RPMS/libobasis3.3-base-3.3.1-8.x86_64.rpm to /var/tmp/portage/app-office/libreoffice-bin-3.3.4/work
/usr/bin/rpm2tar: line 156: ./LibO_3.3.4rc2_Linux_x86-64_install-rpm_en-US/RPMS/libobasis3.3-base-3.3.1-8.x86_64.rpm: No such file or directory
rpm2tar: warning: unable to locate cpio offset (broken/unknown compression?)
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
 * ERROR: app-office/libreoffice-bin-3.3.4 failed (unpack phase):
 *   failure unpacking ./LibO_3.3.4rc2_Linux_x86-64_install-rpm_en-US/RPMS/libobasis3.3-base-3.3.1-8.x86_64.rpm
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_unpack
 *   environment, line 2999:  Called rpm_unpack './LibO_3.3.4rc2_Linux_x86-64_install-rpm_en-US/RPMS/libobasis3.3-base-3.3.1-8.x86_64.rpm'
 *   environment, line 2904:  Called die
 * The specific snippet of code:
 *           rpm2tar -O "${a}" | tar xf - || die "failure unpacking ${a}";


The solution seems simple: just fix the hardcoded versions from the ebuild (required due to weird naming and versions inside the tarball)


-MY_PV2="${PV}rc2"
-BVER="3.3.1-8"
-BVER2="3.3-8"
-UREVER="1.7.0-8"
+MY_PV2="${PV}rc1"
+BVER="3.3.4-401"
+BVER2="3.3-401"
+UREVER="1.7.0-401"
Comment 1 Serkan Kaba (RETIRED) gentoo-dev 2011-08-18 08:40:07 UTC

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