Re: Bug ? rpm -qlp exits with status 0 on I/O error

On Oct 12, 2007, at 11:41 AM, Andre Majorel wrote:

> On 2007-10-10 22:13 -0400, Jeff Johnson wrote:
>> On 10/10/07, Andre Majorel <[email protected]> wrote:
>>
>>> rpm -qlp $file silently exits with status 0 if there's an I/O
>>> error on $file.
>>
>> Fixed:
>>
>> $ rpm -qp glibc-2.6.90-12.i686.rpm ; echo $?
>> 1
>> $ rpm --version
>> RPM version 5.0.DEVEL
>
> Thank you.
>
> A diagnostic to stderr would still be welcome. :-)
>

Sure would, but then the RFE after that is
     Why does rpm report errors twice?

What makes the reporting a bit trickier is that any path that fails
to open as a *.rpm file, will then be opened as a manifest file.

E.g.
     echo "glibc-2.6.90-12.i686.rpm" > b
     rpm -qp b
is equivalent to
     rpm -qp glibc-2.6.90-12.i686.rpm

The error reporting handling w manifest files is rather
different than *.rpm files. Consider what you wish to happen
(extending the previous example)
     touch a
     rpm -qp a b

Should the empty file "a" be an error or not? My personal
preference would be that
     rpm -qp a b
behave like
     rpm -qp `cat a b`

The framework to parse manifests/package files just got
integrated on all arg parsing paths in rpm-5.0 in July,
so I'm quite sure that I will eventually hear all the bugs and RFE's.

Likely more than you wanted to know. Apologies.

73 de Jeff