RPM verification fails when config files are changed
A %verify directive is missing in spec files templates to avoid to error in rpm -V when config files are changed
Facotry and frontend config files should be not verified against modifications (size md5 mtime).
This was noted during OSG tests for 3.3.2
#1 Updated by Marco Mambelli over 3 years ago
- Status changed from New to Feedback
- Assignee changed from Marco Mambelli to Parag Mhashilkar
I added "%verify(not md5 mtime size)" to frontend.xml and glideinWMS.xml
There are other configuration files:
- the ones in /etc/sysconfig
- the web server config
- the condor configs
They are all marked config (noreplace)
Does that mean that changes to any of them are OK (and therefore should be marked as "%verify(not md5 mtime size)")?
#3 Updated by Marco Mambelli over 3 years ago
- Status changed from Feedback to Resolved
The difference with these 2 files is that they are modified automatically (with a script) during the installation process (to replace correct IP).
So only these 2 should be marked to skip verification.
There could be a better way to handle these automatic verifications. To distinguish the automatic changes form the ones done by a sysadmin.