Issue #384
closedRPM requirements with a version but no release show the release as "0"
Description
Description of problem:
Version-Release number of selected component (if applicable):
2.4
How reproducible:
always
Steps to Reproduce:
1. add an RPM (I'm using python-pulp-agent-lib-2.2.0-1) to a repo that has a requirement for a specific version of another package, but does not specify a release.
2. view rpm with: pulp-admin rpm repo content rpm
Actual results:
Requires: python(abi) = 2.6-0, python-pulp-common = 2.2.0-0
Expected results:
Requires: python(abi) = 2.6-0, python-pulp-common = 2.2.0
For this particular package, the requirement can be seen here:
$ rpm -qp --requires python-pulp-agent-lib-2.2.0-1.el6.noarch.rpm
python(abi) = 2.6
python-pulp-common = 2.2.0
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
+ This bug was cloned from Bugzilla Bug #1028491 +
Updated by cduryee almost 10 years ago
This is still the case in pulp 2.4.3
$ pulp-admin rpm repo uploads rpm --repo-id test -f python-pulp-agent-lib-2.2.1-1.el6.noarch.rpm
<successful upload>
$ pulp-admin rpm repo content rpm --repo-id test
Arch: noarch
Buildhost: rhel6-builder
Checksum: 8a2039ab82be77885a7bc171c8bea429c4cddcc0ad344a5f4eec019b35fd1876
Checksumtype: sha256
Description: A framework for loading agent handlers that provide support for
content, bind and system specific operations.
Epoch: 0
Filename: python-pulp-agent-lib-2.2.1-1.el6.noarch.rpm
License: GPLv2
Name: python-pulp-agent-lib
Provides: python-pulp-agent-lib = 2.2.1-1.el6-0
Release: 1.el6
Requires: python(abi) = 2.6-0, python-pulp-common = 2.2.1-0
Vendor: None
Version: 2.2.1
+ This comment was cloned from Bugzilla #1028491 comment 1 +
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
- Severity set to 2. Medium
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.