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.

Bug 677780

Summary: rpm -q --provides not displaying rpmlib() entries
Product: Red Hat Enterprise Linux 6 Reporter: Guil Barros <gbarros>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0CC: jbastian
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 677781 (view as bug list) Environment:
Last Closed: 2011-02-16 06:48:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 677781    

Description Guil Barros 2011-02-15 20:17:58 UTC
Description of problem:
rpm -q --provides not displaying rpmlib() entries

Version-Release number of selected component (if applicable):
rpm-4.8.0-12.el6

How reproducible:
always

Steps to Reproduce:
1. rpm -q --provides rpm

  
Actual results:
# rpm -q --provides rpm
config(rpm) = 4.8.0-12.el6
rpm = 4.8.0-12.el6
rpm(x86-64) = 4.8.0-12.el6


Expected results:
# rpm -q --provides rpm
config(rpm) = 4.8.0-12.el6
rpm = 4.8.0-12.el6
rpm(x86-64) = 4.8.0-12.el6
rpmlib(BuiltinLuaScripts) = 4.2.2-1
rpmlib(CompressedFileNames) = 3.0.4-1
rpmlib(ConcurrentAccess) = 4.1-1
rpmlib(ExplicitPackageProvide) = 4.0-1
rpmlib(FileCaps) = 4.6.1-1
rpmlib(FileDigests) = 4.6.0-1
rpmlib(HeaderLoadSortsTags) = 4.0.1-1
rpmlib(PartialHardlinkSets) = 4.0.4-1
rpmlib(PayloadFilesHavePrefix) = 4.0-1
rpmlib(PayloadIsBzip2) = 3.0.5-1
rpmlib(PayloadIsLzma) = 4.4.2-1
rpmlib(PayloadIsXz) = 5.2-1
rpmlib(ScriptletInterpreterArgs) = 4.0.3-1
rpmlib(VersionedDependencies) = 3.0.3-1


Additional info:
The info can be seen with:
# rpm --showrc rpm | grep rpmlib
Features supported by rpmlib:
    rpmlib(BuiltinLuaScripts) = 4.2.2-1
    rpmlib(CompressedFileNames) = 3.0.4-1
    rpmlib(ConcurrentAccess) = 4.1-1
    rpmlib(ExplicitPackageProvide) = 4.0-1
    rpmlib(FileCaps) = 4.6.1-1
    rpmlib(FileDigests) = 4.6.0-1
    rpmlib(HeaderLoadSortsTags) = 4.0.1-1
    rpmlib(PartialHardlinkSets) = 4.0.4-1
    rpmlib(PayloadFilesHavePrefix) = 4.0-1
    rpmlib(PayloadIsBzip2) = 3.0.5-1
    rpmlib(PayloadIsLzma) = 4.4.2-1
    rpmlib(PayloadIsXz) = 5.2-1
    rpmlib(ScriptletInterpreterArgs) = 4.0.3-1
    rpmlib(VersionedDependencies) = 3.0.3-1

Comment 2 Panu Matilainen 2011-02-16 06:48:58 UTC
This is exactly as it's supposed to be: rpmlib() dependencies can not be satisfied by provides in packages, only the /running/ rpm instance can satisfy them by their very nature.

Say you have a package depending on a new rpm feature, tracked by an rpmlib() dependency, which the currently installed rpm doesn't have:
# rpm -Uvh foo-1.2.i686.rpm
error: Failed dependencies:
    rpmlib(NewFeature) ... is needed by foo-1.2.i686

Unlike regular dependencies, this can't be fixed by adding an updated rpm package into the transaction (eg "rpm -Uvh foo-1.2.i686.rpm rpm-*4.123*.rpm"), because a newer rpm version which brings the support for "NewFeature" must be used to execute the transaction. So you need to first update rpm itself to a version which provides the needed rpmlib() feature, and only then you can install a package using that feature.

Comment 3 Guil Barros 2011-02-17 15:39:24 UTC
So it requires a two-step update?

# rpm -Uvh foo-1.2.i686.rpm
error: Failed dependencies:
    rpmlib(NewFeature) ... is needed by foo-1.2.i686

# rpm -Uvh rpm-2.2.i686.rpm
# rpm -Uvh foo-1.2.i686.rpm

The main concern really is that rpmlib() dependencies look like regular dependencies to the end user but do not show up as regular dependencies, leading to confusion. Maybe we could change the way its presented?