On Tue, Dec 16, 2014 at 06:10:29PM -0500, Jaldhar H. Vyas wrote: > On Tue, 16 Dec 2014, Santiago Vila wrote: > > >>Creating the relevant configuration in postinst is what was broken in the > >>first place. That's why I took it out. > > > >Bug number? References? > > Oh there have been various complaints about this or that use case for a long > time. Unfortunately a lot of correspondence took place outside the BTS but > #706216 and #730828 are examples. [...]
Sorry but I don't follow your line of reasoning. In those examples, the file 10-ssl.conf has SSL certificates by default. But I'm not proposing that the default 10-ssl.conf has SSL enabled anymore. Everything I ask is that we avoid useless prompts in upgrades, which is what this bug is about, and it's also what policy says we should do. So: Why can't dovecot-core create the *current* file (the one *not* having SSL enabled) in the postinst instead of using UCF? Please don't tell me that you already tried that, because you have not. This would solve the problem of UCF asking the same question over and over again on upgrades. Why can't you do that? Using UCF for a file that everybody should change does not make any sense! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
