On Wed, Sep 03, 2008 at 10:34:27AM +0200, Jos Vos wrote:
> On Wed, Sep 03, 2008 at 08:12:43AM +0100, Sam J Sharpe wrote:
> 
> > (if the RPM tagged it as a config file, it would not have been  
> > replaced, [...]
> 
> This is not completely true.  *Only* if the file is marked as
> %config(noreplace) it will never be replaced and the new file
> (if the new rpm includes a different file than the old rpm)
> is stored with a .rpmnew suffix.
> 
> If a file is just marked as %config it can still be replaced, but
> only if the new rpm has a different config file than the old rpm.
> Your own config file (if you had changed that) will then be saved
> with a .rpmsave suffix.

Technically you are right, that's what rpm does. Until %post.

I've had major screw ups if I move ROOTDIR in /etc/syconfig/named,
which is %config(noreplace), but is altered by %post in a way that
ROOTDIR is always reset to the default value resulting in a
non-working bind after any update in the last years:

https://bugzilla.redhat.com/show_bug.cgi?id=451450

What disappoints me a bit is that there is a fix by Red Hat developers
themselves there since February, and alreay tested in the field by
being shipped in Fedora since, but Program Management decided that
this still isn't bug enough for includion in minior RHEL updates. :(
-- 
Axel.Thimm at ATrpms.net

Attachment: pgpgsP0ACyZZw.pgp
Description: PGP signature

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to