On Fri, 2006-06-09 at 14:02 -0500, Mikkel L. Ellertson wrote: > Jonathan Underwood wrote: > > On 09/06/06, Knute Johnson <knute@xxxxxxxxxxx> wrote: > >> There was a recent update to dovecot that caused it to not work. I > >> used yum and deleted the new one and installed the older version. It > >> works fine now. My question is what will yum automatically update > >> dovecot the next time it is run? Do I need to set something to > >> prevent that from happening? How do I know that there is a fix > >> version available if I've disabled updating for dovecot? > > > > There have been several reports that dovecot doesn't work because the > > update configuration file is different, but is installed as > > /etc/dovecot.conf.rpmnew. If you backup /etc/dovecot.conf to a > > different name, rename /etc/dovecot.conf.rpmnew to /etc/dovecot.conf > > and re-enter your config details into the new config file, you may > > well find the updated dovecot works for you. And if not, then it's > > bugzilla time :) > > > > J. > > > I would think it would be bugzilla time in any case. My > understanding is that if the config file format changes, the old > config file gets renamed *.rpmsave and the new config file gets > installed. But I have not been on the RPM list for a long time, so I > could be wrong about this... That depends on how the packager wants to deal with the config file. The usual approach now is to mark config files as "%config(noreplace)" in the rpm spec file. The result of this is that if a new config file is installed and the user has modified the original config file, the original config file is left in place and the new one is installed with a ".rpmnew" extension. On the other hand, if the config file is marked simply as "%config" in the rpmspec file, the user's edited config file will be renamed to have a ".rpmsave" extension and the new config file will be installed in its place. If the user has not edited the config file, the new config file will replace the old one in either case. Paul.
