Site Mail | 1 Dec 2009 13:40
Favicon

Re: Upgrade debian/ubuntu packages messed up my configuration

This time I kept my old config, but in some other upgrade it happened I pressed the wrong key and erased all the settings.
My point is that if you see an upgrade of configuration files and see the maintainer has changed some stuff one could think "hey, new stuff added to default configuration, should be better than the one I have".

So in order to have those changes one have to inspect the files and do the diff and then tweak manually the file. I do not think this should be done like this (as the config file says, the file should only be modified via the admin interface).
An easier approach would be to keep the user config separated from the default config, or even each vhost in its own file?

Lucky me I had copies of my /etc files, so it was not big problem,  etckeeper saved my life!

Thanks for your answers!

On Tue, Dec 1, 2009 at 1:02 PM, Alvaro Lopez Ortega <alvaro <at> octality.com> wrote:
On 01/12/2009, at 12:48, Pablo Hernan Saro wrote:

> So, did the upgrade process messed up your configuration or it was
> because you provided the wrong answer?

No, it's a permissions issue, actually. The configuration file format has not changed.

> Because this is the way package managers deal with configuration
> files. So easy, just answer "keep my configuration file" and you're
> done. BTW, a good practice is to backup config files and other stuff
> before performing software upgrades.

Indeed!

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee

Gmane