Sorry for not responding sooner I was unexpectedly swamped during the new
year.
On Fri, 28 Dec 2012, Dominik George wrote:
The breakage is even worse.
1. The code that causes the problem is intended to set the *new*
path to the certificates. Why the f*** does it print $OLD_SSL_CERT ??
No the idea was that if you have the certs in the old location, only to
update 10-ssl.conf and make sure it has the right configuration
values otherwise leave them alone.
2. NEVER EVER touch user confiuration! It even breaks *own* paths set.
3. Why?
4. Why??
5. Why???
The idea was to move the self-generated certs only. Obviously I did not
consider the scenario where a user had their own certificates but did
not remove the dummy certificates which leads me to...
Here is a patch that leaves site-local confiuration as it is if it does
not reference the default files and only touches it when it referenced
the old default path before. It even uses the *new* path, sih ... did the
maintainer even test this *once*?
I do try and test this package as much as possible and I even had several
other people test it before uploading but they didn't catch this either.
The way Debians process is supposed to work is that packages get uploaded
to unstable and with a wider audience problems will get caught before the
package migrates to testing and mostly it works. But it seems that with
dovecot people wait until it is already in testing before trying it which
defeats the whole scheme.
So what we really need is more testing before an upload even happens. In
theory there is a team maintaining this package but in practice the others
have even less free time than I do and this last year I have had next to
no time at all. (I mean its been 3 weeks since this problem was reported
and I'm only just responding. That would be unacceptable as a user even to
me.) I try and recruit anyone who shows interest but that hasn't worked
either so far. So once again, I ask anyone reading this who cares about
the best possible dovecot package in Debian to pitch in. It's easy to get
access to the source repository and I'll help in anyway I can even giving
you ownership if you can do a better job.
In the meantime I am preparing a new revision which will include your
patch and better documentation of the situation. That's the best I can do
for now.
However, the only valid way to handle this is NOT handle it. Or do the
modification in the ucf template *before* runnin ucf so it is merged
into the confi file if and *only* if the user chooses to apply the
chanes.
Yes all this stuff needs to be moved over to ucf. I had someone offer to
do this before the freeze began but then they disappeared and by that time
it was too late for me to make such an invasive change. (See above.)
--
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
