Product SiteDocumentation Site

4.4.2. Controlling the verification

You can use a number of options to tell the verification command specifically what to check for or not check for. Table 5-9 lists these options.
Table 5-9 Controlling the verification
Option
Usage
--nodeps
Don't verify dependencies.
--nodigest
Don't verify the package or header digests.
--nofiles
Don't verify the file attributes.
--noscripts
Don't try to verify the scripts.
--nosignature
Don't verify the package or header signatures.
--nolinkto
Don't verify the link file attribute.
--nomd5
Don't verify the MD5 digest file attribute.
--nosize
Don't verify the file size attribute.
--nouser
Don't verify the file owner attribute.
--nogroup
Don't verify the file group owner attribute.
--nomtime
Don't verify the file mtime attribute.
--nomode
Don't verify the file mode attribute.
--nordev
Don't verify the file rdev attribute.
-a
Verify all packages in a given group.
-g group
Verify all packages in a given group.
-p file
Verify the given RPM file.
Cross Reference
Chapter 11, Controlling the Build with rpmbuild covers another option for verifying a package file, the rpm –K command.
The --nofiles option is often used with the –Va option to verify the whole system but skip tests of file attributes. This command is used to often it has become an idiom for RPM usage, especially for debugging RPM problems. Run a command like the following:
$ rpm -Va --nofiles