RPM Community Forums

Mailing List Message of <rpm-users>

Re: Detection of "bad" packages

From: Jeff Johnson <n3npq@mac.com>
Date: Mon 01 Aug 2011 - 13:31:28 CEST
Message-id: <42A9C678-73AE-4F19-93C2-7FE212455C4A@mac.com>

On Aug 1, 2011, at 4:42 AM, Michael Baudisch wrote:

> Hello,
> i do some tests with RPM and somehow "bad" packages. When I pass a "bad" test package to RPM I observered that there's an error like "error: open of blablabla failed".  The package is a plain text file  with .rpm extension containing only "blablabla".
> But when I put this "blablabla" in squared brackets ("[Blablabla]") there's no error.
> So, what is the magic that does RPM not detect/report a corrupt package? Are there other circumstances under which RPM does not detect/report a "bad" package? Thanks for help in advance.

What rpm version?

All input arguments that are not *.rpm packages
are treated as a manifest of *.rpm packages.

The manifest is split on white space and each item is added
at that position in the argument list.

Not reporting is not the same as not detecting.
Did rpm actually attempt to install anything?

73 de Jeff
Received on Mon Aug 1 13:32:20 2011
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.