>
> Remember the little discussion over the last couple of days regarding
> RPM not replacing UN-modified config files with the ones from the new
> RPM but rather ".rpmnew"ing them?
>
> I think there was a file marked as a config file (either in the old or
> new RPM) that got installed as a .rpmnew rather than where it should
> have been.
>
> My last cooker update was a complete mess with .rpmnew files. This is
> a serious RPM bug that needs to be fixed immediately.
>
Hmm ... I updated yesterday and got no .rpmnew files. Are you sure, your
configs were really unmodified?
-andrej
