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.
Description of problem:
createrepo computes version strings differently than librpm causing primary.xml metadata to list an incorrect version and release string.
This bug was originally fixed in commit 2269134f119ce13d6a9b725f94954d9dd629f427 in the createrepo git repository, but appears to have been lost during a major internal refactor of createrepo.
Version-Release number of selected component (if applicable):
How reproducible:
Every time
Steps to Reproduce:
A simple test case showing buggy metadata for one package:
0. Install createrepo
1. Download the plexus-cdc-1.0-0.20.a14.el7.noarch.rpm package
2. Run createrepo . in a directory containing plexus-cdc-1.0-0.20.a14.el7.noarch.rpm
3. Read the primary xml metadata
Actual results:
In the provides section of primary.xml.gz:
<rpm:entry name="mvn(org.codehaus.plexus:plexus-cdc)" flags="EQ" epoch="0" ver="1.0" rel="alpha-14"/>
Expected results:
<rpm:entry epoch="0" flags="EQ" name="mvn(org.codehaus.plexus:plexus-cdc)" rel="14" ver="1.0-alpha"/>
Additional info:
Also, I forgot to add that any existing repositories that were generated using this version of createrepo have incorrect metadata showing wrong version and release strings.
Might be a good idea for any important repositories to have their metadata regenerated once this bug is fixed.
This bug is incorrect, version or release strings cannot have a '-' character in them. Only the name can.
rpmbuild has recently been fixed to flag these errors, although I believe the one shipped in rhel-7.0 still lets them through.
Although believe I manually checked all of the packages we shipped for rhel-7, so that none have problem. If you've found any shipped by us though, feel free to open bugs.
I ran a scan using a script I wrote (which could be wrong) that says these packages have issues:
base64coder-20101219-10.el7.noarch.rpm
httpd-2.4.6-17.el7.centos.1.x86_64.rpm
maven-repository-builder-1.0-0.5.alpha2.el7.noarch.rpm
plexus-ant-factory-1.0-0.12.a2.3.el7.noarch.rpm
plexus-bsh-factory-1.0-0.14.a7.el7.noarch.rpm
plexus-cdc-1.0-0.20.a14.el7.noarch.rpm
plexus-component-api-1.0-0.16.alpha15.el7.noarch.rpm
plexus-component-factories-pom-1.0-0.7.alpha11.el7.noarch.rpm
plexus-i18n-1.0-0.6.b10.4.el7.noarch.rpm
plexus-interactivity-1.0-0.14.alpha6.el7.noarch.rpm
plexus-mail-sender-1.0-1.a2.25.el7.noarch.rpm
plexus-resources-1.0-0.15.a7.el7.noarch.rpm
Not sure if these are RHEL-shipped/owned packages or not, sorry.