Bug 3753 - rpm2cpio fails to unpack emgd 1.16 binary rpms
Summary: rpm2cpio fails to unpack emgd 1.16 binary rpms
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.4 M3
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 3718
  Show dependency tree
 
Reported: 2013-01-18 04:16 UTC by Nitin Kamble
Modified: 2013-01-21 16:23 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nitin Kamble 2013-01-18 04:16:15 UTC 
The rpm2cpio generated from oecore native rpm recipe causes these cpio errors:


$ rpm2cpio IEMGD_HEAD_Linux/common/video_plugin/gst-vabuffer-0.10.8-1.i586.rpm | cpio -id

cpio: Malformed number ¤Õ<9f>ª»«ïG
cpio: Malformed number Õ<9f>ª»«ïG¬
cpio: Malformed number <9f>ª»«ïG¬^
cpio: Malformed number ª»«ïG¬^^P
cpio: Malformed number »«ïG¬^^P<97>
cpio: Malformed number «ïG¬^^P<97>Ú
cpio: Malformed number ïG¬^^P<97>Ú{
...


How to reproduce the issue:

1. Download this tarball: 
  https://edc.intel.com/App_Shared/Downloads/LIN_IEMGD_1_16_GOLD_3228.tgz

2. Unzip the above downloaded tarball

3. Use the rpm2cpio generated by native rpm recipe of YP to unpack an RPM with a command like this:
  $ rpm2cpio IEMGD_HEAD_Linux/common/video_plugin/gst-vabuffer-0.10.8-1.i586.rpm | cpio -id 


You will see the errors as seen above.

Also FYI the rpm2cpio provided by build system's distro (OpenSuSE 11.4) works fine with these emgd 1.16 RPMS.
Comment 1 Mark Hatle 2013-01-18 22:55:17 UTC 
My guess is that whomever created the gst-vabuffer rpm package did so using non-compatible configurations.

Specifically recent versions of Fedora Linux's version of RPM enable suppose for alternative compression methods.  If these methods are used, and the rpm2cpio shell script don't understand them, it will not be possible to extract the items.

My suggestion is to get a copy of the latest rpm4 from Fedora, and see if they have an updated rpm2cpio script (not the executable).  If this can extract that package, the changes may need to be ported to our version.