Bug#856067: unblock: amavisd-new/1:2.10.1-4
Control: tag -1 confirmed
Hi,
On Sat, Feb 25, 2017 at 09:39:51AM +1100, Brian May wrote:
> Request dialog concerning amavisd-new situation.
>
> amavisd-new has a release critical bug. #847311. The justification given
> was "causes non-serious data loss" presumably because emails were being
> incorrectly classified as SPAM. This only happened for people using the
> mysql functionality which is an optional feature of amavisd-new. I do
> not agree this makes it RC, however I have not tried to change it,
> however an earlier attempt to change it to important resulted it in
> being changed back to grave.
I agree that it's not obviously RC - there seems to have been a
misunderstanding on Adrian's part there (however well-meaning).
> The bug is not a bug in amavisd-new. It is a bug in libdbd-mysql-perl.
> I have opened a bug #856064 (grave). There is an upstream patch:
>
> https://github.com/perl5-dbi/DBD-mysql/pull/102
>
> It has been proven to fix the problem:
>
> https://github.com/perl5-dbi/DBD-mysql/issues/78#issuecomment-282270330
>
> So question is, where do we proceed from here? I guess first step would
> be to wait for a response for #856064.
>
> I am also guessing tha since amavisd-new has already been removed from
> testing, there is no chance of getting it back in. If this is the case,
> is there any chance of getting it back into a future point release?
Not in a point release, but I'll cut you a deal: if the underlying bug in
libdbd-mysql-perl is fixed (but *without* the additional fixes Pali
mentions), and an unblock bug opened before 1st March, I'll unblock
amavisd-new and amavisd-milter for stretch.
(no precedents, subject to future developments, blah, blah, etc, etc).
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: