Red Hat Bugzilla – Bug 180270
rhn-applet: rpm verify fails due to config files in .spec not marked with %verify
Last modified: 2007-11-30 17:07:23 EST
+++ This bug was initially created as a clone of Bug #180268 +++
Description of problem:
The TPS rpm --verify tests fail because the /etc/sysconfig/rhn/rhn-applet config
file will always be different from default. Why? Because the uuid field gets
populated during the installation process. The spec file needs to be flagged
with approriate %verify bits so it passes this test.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Blocking rhnupr4u4 and rhnupr3u8 to track the progress of the release
Should be fixed in CVS.
See also: bug #180268
*** Bug 185697 has been marked as a duplicate of this bug. ***
i386, ia64, x86_64, s390, s390x, ppc
All had a timestamp change on the config file. Should timestamp be added to the
list of excludes as well?
[root@test01-ia64 tmp]# rpm -V rhn-applet
........C c /etc/sysconfig/rhn/rhn-applet
Hmm. After further research, I see that this is not timestamp related at all.
This is some sort of "context" flag. It means that the context stored in the
file's extended attribute on disk is inconsistent with the file_contexts
configuration. To fix, run /sbin/restorecon on the file(s) in question.
So, should "context" be added to the list of excludes? Is that even allowed?
ok - this has been fixed by adding the following to the %post section:
chcon system_u:object_r:etc_t /etc/sysconfig/rhn/rhn-applet
verified on s390, s390x, ppc, ia64, i386, and x86_64 with package
rpm -V now gives empty response
TPS tests *should* pass. Let's hope so.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.