Package: release.debian.org Severity: normal User: [email protected] Usertags: unblock
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. 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? I believe amavisd-new is a somewhat popular package, not including it in the next release is going to inconvenience a large number of people. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
