On Mon, Dec 15, 2014 at 10:02:56PM +0100, Santiago Vila wrote: > Suppose I had the old configuration file served by puppet. The upgrade > modifies the file, then puppet restores the file to its original state. > Then the next upgrade will change the file to the new ucf default, > which may be completely unsuitable for my system.
I forgot a minor detail: If the file is managed by puppet, there would be nothing to worry about, right? No, I don't think so: 1. I upgrade dovecot-core to the current version 2. postinst modifies the file 3. puppet restores the file and removes the added comment line 4. the next upgrade of dovecot-core upgrades to the ucf default which does not work 5. puppet restores the file again The problem is the time window between 4 and 5 in which dovecot will not work at all. Note: I have a linode running wheezy and I want to upgrade it to jessie. For now I'm running upgrade simulations using qemu and I am naturally keeping an eye on the upgrade problem that this package had, but even if it has been reported that the upgrade now "works", I believe that the current solution to the upgrade problem is too hacky. My previous question remains: Why the file is managed by UCF at all? Would be possible to consider keeping the certificate generation code (and ssl=yes) in jessie as a better solution to the upgrade problem? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
