what to do with .rpmnew's?

[Jeff Vian]

On Fri, 2005-07-15 at 20:15 -0400, Claude Jones wrote:
> On Friday 15 July 2005 6:25 pm, ne... wrote:
> > On 7/15/05, Claude Jones <claude_jones at levitjames.com> wrote:
> > > *** warning: /etc/rndc.key created as /etc/rndc.key.rpmnew
> > > *** warning: /etc/selinux/targeted/contexts/files/file_contexts.homedirs
> > > saved as
> > > /etc/selinux/targeted/contexts/files/file_contexts.homedirs.rpmsave
> > >
> > > Running updates today, and got the above warnings. What's the proper
> > > reaction? These are configuration files that are being replaced for some
> > > reason, but the old are being renamed and kept in case there's something
> > > needed in one of them? Do I have this right?
> >
> > The one with rpmsave is the old one being saved. The one with rpmnew
> > is what was in the rpm you installed and does not overwrite the current
> > file.
> >
> 
> So, there's the original file, which is left untouched; that file is copied 
> with the extension .rpmsave and still left untouched; and the new default 
> file that the upgrade 'would' have installed is saved with the 
> extension .rpmnew - correct so far? 
> 

Not quite. There are 2 different approaches here.

1.  If the original file is untouched the replacement will be named
with .rpmnew.
or
2. If the original is replaced the original gets named with .rpmsave.

> I'm still not sure what I'm supposed to do with these. 
> 
> How do I decide whether to use the new default file, or leave things as they 
> are with the original file? I guess in some cases, the answer is obvious, if 
> I've made custom configurations, but, what is the general procedure, here?  
> 
In either case you can see both your original and the replacement so you
are able to merge in any customizations needed.

> 
> -- 
> Claude Jones
> Bluemont, VA, USA
>