> > full patch attached -- I just want to hear your feedback first and
> > then will do additional testing to assure correct behavior on a stable
> > system
> Well, even lenny has "python" as 2.5, so the double try shouldn't really
> be necessary.  Other than that, please go ahead; thanks.

it just was taken from upstream commit and upstream is still 2.4
compatible -- I saw no reason to tune it up

> > Major change is to deal with grave:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650678
> > which prevented use of fail2ban with multiple jails enabled.  It has
> > been in unstable and testing for a while and I have not heard about any
> > negative  feedback
> #554162 was a more useful reference there, imho.
> > (quilt)) suggested NMU
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635746
> Likewise #544232, as the newer bug is purely about the suggested NMU,
> not what the actual problem was.

so -- in general -- should I list all of them as well (even those closed
and archived in sid)?  ignorantly I thought that it should be still open
squeeze-tagged bug reports...

-- 
=------------------------------------------------------------------=
Keep in touch                                     www.onerussian.com
Yaroslav Halchenko                 www.ohloh.net/accounts/yarikoptic


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120218184423.gs16...@onerussian.com

Reply via email to