[BlueOnyx:05101] Re: Ref: .rpmnew files in an old BO server

[Stephanie Sullivan]

> -----Original Message-----
> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-
> bounces at blueonyx.it] On Behalf Of Michael Stauber
> Sent: Saturday, July 24, 2010 11:28 AM
> To: BlueOnyx General Mailing List
> Subject: [BlueOnyx:05100] Re: Ref: .rpmnew files in an old BO server
> It works like this: Some RPMs have config files. Typically those
> config files
> have some defaults in them, but on a running system the config files
> have seen
> some (needed!) updates and changes, which you don't want to loose.
> 
> To prevent loss of data in such config files during RPM updates, the
> RPM
> mechanism allows to specify such config files with the flag
> "noreplace". So
> when you install an upgraded version of a certain RPM, it'll check if
> there is
> already a config file present and it will also check if that config
> file has
> been modified since it was installed.
> 
> If the RPM mechanism detects that the config file of the older RPM
> has been
> modified, it will not overwrite it with the "stock" version from the
> newer
> RPM. Instead the config file from the newer RPM will be installed as
> *.rpmnew
> 
> So simply ignore the *.rpmnew files. The system takes care of itself
> there.
> 
> With best regards
> Michael Stauber

How I wish BX (and BQ) updates worked that way...

	Thanks,
		-Stephanie