Re: iptables sarge release

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Steve Langasek <vorlon@debian.org> writes:

> On Sun, May 08, 2005 at 06:15:00PM -0500, Laurence J. Lane wrote:
>> There are a couple of iptables bugs that missed the standard
>> freeze. #283822 in particular is scripting error that causes
>> a FTBFS when using a dash (and probably other shells) instead
>> of bash.
>
>>   iptables (1.2.11-10) unstable; urgency=medium
>
>>     * fixed scripts/prep.sh: patching and patch ordering
>>     * fixed a bashism reported by Geller Sandor in Bug#283822. Thanks.
>
>>    -- Laurence J. Lane <ljlane@debian.org>  Wed,  1 Dec 2004 19:11:34 -0500
>
>>   iptables (1.2.11-9) unstable; urgency=medium
>
>>     * another prep.sh tweak for patch ordering
>>     * Bug#283721, Policy match save code puts in line feed that makes
>>       iptables-restore error, reported and fixed by Matthew Grant. Thanks.
>
>>    -- Laurence J. Lane <ljlane@debian.org>  Tue, 30 Nov 2004 23:04:01 -0500 
>
> Approved.
>
> Thanks,
> -- 
> Steve Langasek
> postmodern programmer

There is another bug caused by different alignment on i386 and amd64
causing 32bit iptables to not work under a 64bit kernel. I'm not sure
how complicated the patch will be but it looks to be localised to one
file and function only.

Is that likely to get accepted to sarge too and should I hurry to make
a patch?

MfG
        Goswin