| Summary: | rpm -qf output is ambigous for multiple arguments and multiple file owners | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter Backes <rtc> |
| Component: | rpm | Assignee: | Fedora Packaging Toolset Team <packaging-team> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | ed, ffesti, pknirsch, pmatilai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 14:06:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Please reopen this bug as it still applies to currently supported Fedora versions, e.g. Fedora 20. Thanks for resetting the bug status to NEW - please could you also change the Version field to 20, or set up the permissions so that others can do so? Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: rpm -qf works by looking up the packages that own the files specified as an argument, then perform the query operation. During this two-step process, the relation of query end result to the initial files queried is lost and currently cannot be recovered by queryformat. Thus, the output may be ambigous if multiple arguments are specified. This kind of use is common for mass queries where the speed of invoking rpm -qf separately for each argument would not be acceptable, like find | xargs rpm -qf, Version-Release number of selected component (if applicable): rpm-4.9.1.2-5.fc16.i686 How reproducible: always Steps to Reproduce: 1. cd /usr/share 2. rpm -qf sgml a2ps Actual results: sgml-common-0.6.3-34.fc15.noarch GConf2-3.2.3-1.fc16.i686 xml-common-0.6.3-34.fc15.noarch a2ps-4.14-12.fc15.i686 It is not possible to tell from the output alone which of the packages are owned by which of the files. Thus, the output is essentially pretty useless. Expected results: Unambiguous output, or at least some way to refer to the initial argument/file in the query format, like rpm -qf --qf "%{FILE} %{NAME}\n" sgml a2ps /usr/share/sgml sgml-common-0.6.3-34.fc15.noarch /usr/share/sgml GConf2-3.2.3-1.fc16.i686 /usr/share/sgml xml-common-0.6.3-34.fc15.noarch /usr/share/a2ps a2ps-4.14-12.fc15.i686 Additional info: There is a workaround, though a pretty ugly one: specify some non-existing file as every second argument, as follows: rpm -qf /name/sgml sgml /name/a2ps a2ps 2>&1 error: file /name/sgml: No such file or directory sgml-common-0.6.3-34.fc15.noarch GConf2-3.2.3-1.fc16.i686 xml-common-0.6.3-34.fc15.noarch error: file /name/a2ps: No such file or directory a2ps-4.14-12.fc15.i686 the error messages can be used to disambiguate the output. For mass queries using xargs, this more than doubles the rpm invocations, however.