Querying for a package by arch can lead to odd (lack of) output in some cases. Easiest to show with an example: [katzj@erebor creator]$ rpm -q bash bash-0:3.2-9.fc7.x86_64 [katzj@erebor creator]$ rpm -q bash.x86_64 bash-0:3.2-9.fc7.x86_64 [katzj@erebor creator]$ rpm -q bash.i386 [katzj@erebor creator]$ rpm -q foo package foo is not installed [katzj@erebor creator]$ rpm -q foo.i386 package foo.i386 is not installed I'd expect the query for bash.i386 to say that it's not installed.
That goes somewhat deeper. Watch this: $ rpm -q bash ; echo $? bash-3.2-9.fc7 0 $rpm -q bash.x86_64 ; echo $? bash-3.2-9.fc7 0 $ rpm -q foo ; echo $? package foo is not installed 1 $ rpm -q foo.i386 ; echo $? package foo.i386 is not installed 1 $ rpm -q bash.i386 ; echo $? 0 Clearly your rpm is configured in some non-default way if it responds with 'bash-0:3.2-9.fc7.x86_64' but that is not the issue.
This is a dupe of another bug report (by D. Hugh Radimier iirc). UPSTREAM
*** This bug has been marked as a duplicate of 124016 ***