Steve Langasek wrote:
I've just uploaded ipsec-tools_0.5.2-1_i386.deb and racoon_0.5.2-1_i386.deb (source package ipsec-tools-0.5.2) to unstable. The version in testing is 0.5.1-1. Even though upstream version has changed, this is a purely bug fix release and has some important fixes that should get into sarge.I have been pushing upstream for this release for a few days and the release was made just today. Do I also need to upload to testing-proposed-updates or will the unstable version be pushed automatically?Please read the guidelines provided in the freeze announcement about what updates are being accepted during the freeze, and wehat information the release team needs to be able to approve a request.
Sorry, I missed the changelog and bug numbers information about the uploads. The following are the changelog from the version in sarge:
========
ipsec-tools (1:0.5.2-1) unstable; urgency=high
* New upstream release. This release fixes ph2handle unlink bug
(closes: #307233).
* Urgency high because of fix for security problem with single DES.
* Applied patch from Richard Lucassen to pass options to racoon via
/etc/default/racoon file.
-- Ganesan Rajagopal <rganesan@debian.org> Wed, 4 May 2005 13:46:45
+0530
ipsec-tools (1:0.5.1-2) unstable; urgency=low
* Disabled readline support because it introduces a bug in setkey and
confuses a lot of people (closes: #303573).
* Added Build-Conflicts for bison++ (closes: #305974).
-- Ganesan Rajagopal <rganesan@debian.org> Mon, 2 May 2005 10:18:04
+0530
========Even though the single DES fix is security sensitive, nobody in their right mind should be using single DES any way. So the real critical issues are the fixes for Bug#307233 and Bug#303573. I believe these fixes warrant pushing ipsec-tools-0.5.2 into sarge. The package is priority extra. Thanks.
Ganesan