[Rpm-maint] rpm --verify -p does not work

Panu Matilainen pmatilai at laiskiainen.org
Wed May 25 11:43:08 UTC 2011

On 05/16/2011 11:40 AM, Panu Matilainen wrote:
> On 05/13/2011 04:11 PM, Michael Schroeder wrote:
>> On Fri, May 13, 2011 at 03:49:37PM +0300, Panu Matilainen wrote:
>>> Hmm. Collections aside, me thinks the actual bug is permitting verify to
>>> run on non-installed packages in the first place, verify (and
>>> verifyscript) is only meaningful for installed packages.
>> Ah well, there's a use case: If you don't trust the content
>> of the rpm database because your system was compromised you can
>> still check if somebody messed with a file. I like that
>> functionality, and it seems easy to support.
> Oh, I hadn't thought of that use-case. Fair enough.

Ok, fixed in HEAD now based on your patch with slight differences:
- call rpmpsmRun() directly from rpmVerifyScript() instead going through 
rpmteProcess() which only adds further complications with no added value 
to this (%verifyscript is rather special case among the scriptlets anyway)
- skip collections on all script stages in rpmteProcess()


	- Panu -

More information about the Rpm-maint mailing list