-V for verify -a for all packages -nomtime do not care about modification time
The format of the output is a string of 8 characters, a possible attribute marker:
- c %config configuration file.
- d %doc documentation file.
- g %ghost file (i.e. the file contents are not included in the package payload).
- l %license license file.
- r %readme readme file.
from the package header, followed by the file name. Each of the 8 characters denotes the result of a comparison of attribute(s) of the file to the value of those attribute(s) recorded in the database. A single “.” (period) means the test passed, while a single “?” (question mark) indicates the test could not be performed (e.g. file permissions prevent reading). Otherwise, the (mnemonically emBoldened) character denotes failure of the corresponding –verify test:
- S file Size differs
- M Mode differs (includes permissions and file type)
- 5 MD5 sum differs
- D Device major/minor number mismatch
- L readlink(2) path mismatch
- U User ownership differs
- G Group ownership differs
- T mTime differs
- P caPabilities differ
If you found this post or this website helpful and would like to support our work, please consider making a donation. Thank you!Help Us
Articles in the same category
- yumdownloader how to download RPM package without installing it
- yumdownloader comment télécharger un RPM sans l'installer
- RPM What files have been changed ? -- Verify System Files
- How to turn off / avoid brp-python-bytecompile script in a spec file ?
- How to list / find out what files are in rpm package ?
- Comment déterminer l'ensemble des fichiers dans un paquet rpm ?
- Comment désactiver/éviter le script de brp-python-bytecompile dans un fichier spec ?