Bug 2945

Summary: rpm2cpio fails
Product: [Build System, Metadata & Runtime] BSPs Reporter: Nitin Kamble <nitin.a.kamble>
Component: bsps-meta-intelAssignee: Rahul Saxena <rahul.saxena>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: mark.hatle, meta.mr.watcher, meta.watcher, rahul.saxena, ross.burton, sgw, sstncr, tom.zanussi
Version: unspecified   
Target Milestone: 1.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard: (autobuilder)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Nitin Kamble 2012-08-15 05:01:39 UTC 
This is hitting cedartrail BSP building, because it has a binary recipe needing rpm2cpio. This issue does not happen with the distro provided rom2cpio.



ERROR: Logfile of failure stored in: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.31308
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| rpm2cpio.real: signature.c:860: verifyDSA: Assertion `sigp->pubkey_algo == (rpmuint8_t)PGPPUBKEYALGO_DSA' failed.
| cpio: premature end of archive
| ERROR: Function failed: do_configure (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.31308 for further information)
NOTE: package cdv-pvr-driver-1.0-r1.1: task do_configure: Failed


Build status: FAILURE
Buildslave for this Build: ab07 
Complete logs for all build steps: http://autobuilder.yoctoproject.org:8010/builders/cedartrail/builds/143 
Build Reason: Triggerable(cedartrail) 
Build Source Stamp: [branch 1.3_M3] 8b8748c8f963900b83dc0fdd7757556f917fe4fd 
Detailed log of last build step: http://autobuilder.yoctoproject.org:8010/builders/cedartrail/builds/143/steps/shell_27/logs/stdio
Comment 1 Nitin Kamble 2012-08-15 05:04:09 UTC 
Rahul, are you working this issue ?
Comment 2 Mark Hatle 2012-08-15 15:37:23 UTC 
The error is actually correct.  The binary RPM you are trying to extract does 
not have a valid signature, so it's preventing the extraction.  (This is 
something fairly new in RPM 5.4.5 or so..)

There are two ways "around" the issue.  The first is simply sign the package. 
Once it's signed, the signature can be used to validate the package.

The alternative is to use the shell script version of rpm2cpio which does not 
perform any validations.  In this case, this is probably adequate.

Run "rpm2cpio.sh" instead for the extraction process.. there is a copy in 
scripts already.
Comment 3 Rahul Saxena 2012-08-15 15:57:18 UTC 
Nitin, For cedartrail BSP I am going to replace rpm2cpio with rpm2cpio.sh. I will be sumbitting this patch along with a patch to upgdare the PVR driver rev to 1.0.2 in next few days.
Comment 4 Ross Burton 2012-08-21 10:08:40 UTC 
I do wonder why rpm2cpio doens't have an option to skip signature validation, or why it doesn't give a sensible error when there isn't a signature to validate...

Rahul, I saw the patch series to upgrade the versions, is there a patch coming to fix this too?
Comment 5 Rahul Saxena 2012-08-21 13:50:23 UTC 
Ross,The patches I had submitted were for the Denzel branch, this issue does not impact the Denzel branch. I will be submitting patches for the master branch too in a few days, these will include the fix for the rpm2cpio issue.
Comment 6 Ross Burton 2012-08-29 09:36:18 UTC 
This is still failing on the autobuilder, are there patches queued for oe-core master yet?
Comment 7 Rahul Saxena 2012-08-30 20:32:27 UTC 
(In reply to comment #6)
> This is still failing on the autobuilder, are there patches queued for
> oe-core master yet?

The patches to fix this issue in master branch were added on the 27th Aug. So you should not see this issue if you are including the commit (eaf696e19ed97745a879e42fffb94423aabe27e4) that includes this patch.
Comment 8 Rahul Saxena 2012-09-20 17:50:51 UTC 
I rebuilt my cedarimage and verifed that the issue has been fixed.
Comment 9 Stefan Stanacar 2012-10-02 10:36:11 UTC 
Verified.