Bug 132011 - rpm arch-specific query output is inconsistant
rpm arch-specific query output is inconsistant
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-09-07 16:59 EDT by Joshua Jensen
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-07 21:01:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joshua Jensen 2004-09-07 16:59:29 EDT
Description of problem:

#I have one kernel package installed
[jjensen@asic-amd32 jjensen]$ rpm -q kernel --qf '%{name}\t%{arch}\n'
kernel  x86_64

#I ask about a non-existant kernel
[jjensen@asic-amd32 jjensen]$ rpm -ql kernel.i789
package kernel.i789 is not installed

#I ask about another non-existant kernel
[jjensen@asic-amd32 jjensen]$ rpm -ql kernel.i386
(nothing showing for an error)

Isn't that inconsistant?  I can't get any error messages for the query
of a non-existant package.

Furthermore, rpm isn't even throwing an error code:

[jjensen@asic-amd32 jjensen]$ rpm -ql kernel.i386 &&  echo xyz

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

Comment 1 Jeff Johnson 2004-09-07 21:01:50 EDT
rpm trims known tokens from the tail of the arg iff recognised.

The string ".i386" is recognised, and hence trimmed.

The string ".i789" is not recognized, and hence not trimmed.

Retrofitting an .arch marker can/will collide with, say, a
package named "kernel.i386".

Don't do that is about all I can suggest. There are no easy answers
to retrofiiting new, multilib peculier, token parsers.

Note You need to log in before you can comment on or make changes to this bug.