Shared publicly  - 
#rant #sigh "_warning: foo.conf created as foo.conf.rpmnew" Ten years ago I had expected to rarely see messages like this it any more in 2013. But they IMHO still show up way to often(¹), as too many software still doesn't use the tricks(²) to avoid the hassle. It's one imho, as once in a while those rpmnew files contain important configuration values that break things if you don't merge them back into your configuration :-/

(¹) In this case for example, as this screenshot is from a test vm where I never configured a printer or otherwise touched the cups configuration :-/
(²) among them afaics: (1) sane default configuration somewhere in /usr/ and a empty file in /etc/ that only contains what's actually needed (including overrides) (2) config snippets that can be placed in subdirectories (/etc/modprobe.d/, /etc/X11/xorg.conf.d/)
Mace Moneta's profile photoHeiko “Ostfriese” Adams's profile photoThorsten Leemhuis's profile photoStefan Nickl's profile photo
They are everywhere.  Seriously, /etc/issue.rpmnew and /etc/!?

# locate rpmnew
Big +1 to what +Kay Sievers said. Albeit that's one of those situations where I wonder if distributions should work together more closely and send upstream (that's where most of the hard work needs to be done afaics) a strong message to finally get their act together. I guess makeing the problem uderstood everywhere might be one of the most important things, as it seems too many developers are not aware of the problems they cause with their 80s-like approach to configfiles, /etc/ and such :-/
IMHO config files should be generated at first start of a app/daemon etc and not be shipped by vendors.
+Björn Gerhart what RPM does and supports wrt to config files are workarounds to make dealing with current software bearable; the proper solution is to fix the software instead so RPM normally does not have to deal with this stuff (see the "The first thing a modern OS" part in Kays comment).
Add a comment...