On Thu, 27 Dec 2012, Jerry Quinn wrote:
I was bitten by the same bug. I'm certainly not an *advanced* user of
dovecot. When I first set up dovecot it worked perfectly for me out of the
box. I had no idea where to look without seeing the original reporter's
workaround.
and
On Fri, 28 Dec 2012, Daniele Nicolodi wrote:
I experienced the same problem. It is really annoying that a previously
working configuration breaks on a minor package upgrade.
I sympathize, I really do but may I point out that this is now documented
in /usr/share/dovecot-core/NEWS.Debian.gz. It is your responsibility to
read changelogs, NEWS.Debian, README.Debian etc to find out what has
changed before upgrading. (Though I'm sure I could do a better job of
documentation. Feel free to ding me on that.)
This wasn't a minor upgrade. Much work was done to get dovecot working
the way it is supposed to. It is only happy coincidence that some things
worked in the past; they were not, strictly speaking, features.
The solution I suggest is to have a script that replicates dovecot
mailbox auto detection and writes the relevant configuration entry
during the upgrade process. It should not be too difficult to implement.
I can help with such a script, but I don't know enough ucf to handle the
creation/modification of the configuration file during upgrade.
The other problem I am facing right now is that Debian is in a freeze for
the next version and so I can't make drastic changes to the package. In
the future I will use ucf. However given the complexity of this software
and the wide variety of uses it is put to, there will always be manual
configuration involved.
--
Jaldhar H. Vyas <jald...@debian.org>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
