On Fri, May 20, 2005 at 08:48:51AM +0200, Rene Mayrhofer wrote: > Am Freitag, 20. Mai 2005 07:10 schrieb Steve Langasek: > > I'm happy to let openswan 2.3.0-2 in now if the maintainer thinks it's > > ready, but IIRC he had some other concerns about 2.3 that were unrelated to > > this bug. Rene? > Yes, a pluto (IKE daemon) crash that is triggered by openswan 2.3.(0|1). > People tell me that it's rare, but at least in my setup it's reproducable. > I would indeed feel more comfortable with 2.2.0-5 (which works perfectly well > on all of my production boxes, with kernels 2.4.X with the openswan stack and > with Debian default kernels with 26sec). Is there anything that I can do to > revive that version (which got removed from testing due to my failure to mark > the RC bug sid.... I am very sorry about that). The only sane way to get 2.2.0-5 back into testing now would be with an epoched upload to unstable. I'd still be happy to let it into sarge if you wanted to do this, as I agree with those who say it's an important piece of software; even so, bringing the package back any other way than through unstable just has too much risk. Thanks, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature