Hi Tobias, Thanks you for having a look into the issue.
On Sat, 8 Dec 2012 04:05:16 Tobias Kranz wrote: > this bug has been marked as release-critical for Debian Wheezy and should > therefore > be fixed before Wheezy is released. While the bug has already been fixed in > version 1:2.0.1+dfsg-1, it is still present in version 1:1.8.11-1. Since > Wheezy > has already been frozen, version 1:2.0.1+dfsg-1 contains too many changes > to be migrated automatically into Wheezy and the bug remains therefore > open. We have an unblock request (#687916) for 1:2.0.2+dfsg-4 with release team so we're waiting for their decision. We still have some (fading) hope that 2.0.2 can be unblocked. The situation is quite extraordinary: although Zabbix was staged in unstable too late to satisfy freeze policy, there were not a single bug reported since upload of 1:2.0.2+dfsg-4 ~114 days ago. The problem will be gone if 2.0.2 will be allowed to migrate -- otherwise we will request removal of 1.8.11 from testing and upload to wheezy-backports. > You should therefore cherry-pick the patch which fixes this particular > issue described in this bug report and rebuild the package 1:1.8.11-1 for > Wheezy and have your mentor upload the package. It would also be nice if > you could attach the > patch to this bug report to help others trying to fix this issue for > Wheezy. Even if this particular problem could be easily fixed (which is not the case) there are some other security issues that make 1.8.11 unsuitable for release. Regards, Dmitry.
signature.asc
Description: This is a digitally signed message part.
