Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionThierry Vignaud
2011-02-01 15:24:31 UTC
Created attachment 476415[details]
fix rpm2cpio.sh on RHEL6
Description of problem:
/usr/lib/rpm/rpm2cpio.sh isn't able to extract files from rhel6 rpms due to the payload change (gzip compressed cpio archive -> xz compressed one)
Attached patch fixes it
Version-Release number of selected component (if applicable):
rpm-4.8.0-12.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. run that script on any package:
2.
3.
Actual results:
Error message:
/usr/lib/rpm/rpm2cpio.sh libudev-147-2.29.el6.x86_64.rpm
/usr/lib/rpm/rpm2cpio.sh: line 35: return: can only `return' from a function or
Expected results:
It should output a cpio archive like in the old days.
Additional info:
This is due to the payload format change between RHEL5 & RHEL6
Well I never said it was critical :-)
Still it's usefull when rpm is broken (shouldn't happen on RHEL but I've see usefull cases of rpm2cpio.{sh,pl} on desktop distros.
It's also usefull when trying to rebuild a newer SRPM on RHEL5.x
It can go as it into trunk and rpm-4.9.
It wouldn't hurt backporting it into the 4.6 branch, waiting for next security and/or fixes release.
I won't cry about it not being in RHEL just now (else I would have filled RHN instead :-))
Btw, I saw yesterday it's fixed in rpm-5.3 (not that I care about jbj stuff but it has slightly better logic that mine for handling xz/lzma). On the other hand, I did test my patch whereas I didn't test the "other" one.
See you
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1737.html
Created attachment 476415 [details] fix rpm2cpio.sh on RHEL6 Description of problem: /usr/lib/rpm/rpm2cpio.sh isn't able to extract files from rhel6 rpms due to the payload change (gzip compressed cpio archive -> xz compressed one) Attached patch fixes it Version-Release number of selected component (if applicable): rpm-4.8.0-12.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. run that script on any package: 2. 3. Actual results: Error message: /usr/lib/rpm/rpm2cpio.sh libudev-147-2.29.el6.x86_64.rpm /usr/lib/rpm/rpm2cpio.sh: line 35: return: can only `return' from a function or Expected results: It should output a cpio archive like in the old days. Additional info: This is due to the payload format change between RHEL5 & RHEL6