[SOLVED] RPM's handling of config files, not working for me

[action_owl]

I am not seeing the handling of config files as described the "Maximum RPM" guide, and I'm hoping an experience packager can lend me some brain cycles.

I have a file scenario as described by http://www.rpm.org/max-rpm/ch-rpm-up...FIG-FILE-MAGIC:

Original file = X, Current file = Y, New file = X

Here we have a file that was changed at some point. However, the new file is identical to the existing file prior to the local modifications.

In this case, RPM takes the viewpoint that since the original file and the new file are identical, the modifications made to the original version must still be valid for the new version. It leaves the existing, modified file in place.

What is happening to me, is that RPM is overwriting the the current configuration file that has been modified, there is not an ".rpmsave" or ".rpmorig" version of the file or any warnings when I update.

The file is that is being overwritten is defined in the %files section of my specfile, I have no warnings when building the rpm and I have tried bumping both the Version and the Release.

[PabloTwo]

Here is an example from one of my rpm packages on how to use the %config(noreplace) declaration on the configuration files that you do not want to be "replaced" or overwritten.

%files
%defattr(-,root,root,-)
%{_bindir}/*
%dir %{_sysconfdir}/rmsgw
%{_sysconfdir}/rmsgw/*
%config(noreplace) %{_sysconfdir}/%{name}/gateway.conf
%config(noreplace) %{_sysconfdir}/%{name}/channels.xml
%config(noreplace) %{_sysconfdir}/%{name}/banner
%config(noreplace) %{_sysconfdir}/%{name}/hosts
%{_mandir}/man?/*
%doc COPY* INSTALLING History

In the example above, any update to this package would install the "new" config files as "filename.rpmnew" if the currently installed config file was modified from it's original state and leave the modified config file untouched.

[action_owl]

Thanks PabloTwo!
That appears to be the piece I was missing!