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:

Imagine there is a package installed for multiple architectures, like i.e.

libdwarf-20130207-3.el7.x86_64
libdwarf-20130207-3.el7.i686

Then when the version needs to be extracted by the --queryformat, it produces invalid output:

rpm -q --queryformat '%{VERSION}' libdwarf

Version-Release number of selected component (if applicable):

rpm-4.11.1-16.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1. install some package for both primary and secondary arch
yum install libdwarf.x86_64 libdwarf.i686
2. VERSION=`rpm -q --queryformat '%{VERSION}' libdwarf`
3. echo $VERSION

Actual results:

2013020720130207

Expected results:

20130207

Additional info:

Maybe it's not a bug, but it breaks the usage of rpm -q with queryformat. The version should be the same in multilib, but when it's used in a script it may return the doubled string and cause problems.

This is the expected behaviour. rpm -q lists the result of all matching packages. If you want the '%{VERSION}' of one exact package please specify the package unambiguously on the command line. To get nice looking results for multiple packages use rpm -q --queryformat '%{VERSION}\n' instead.