On 06/01/2008, Tom Eastep <[EMAIL PROTECTED]> wrote:
> Yes. The following is the only hunk which should be omitted:
>
> diff -Naur -X /home/teastep/shorewall/trunk/tools/build/exclude.txt
> shorewall-perl-4.0.7.1/Shorewall/Tc.pm shorewall-perl-4.0.7.2/Shorewall/Tc.pm
> --- shorewall-perl-4.0.7.1/Shorewall/Tc.pm 2007-11-16 07:57:37.000000000
> -0800
> +++ shorewall-perl-4.0.7.2/Shorewall/Tc.pm 2008-01-02 08:02:43.000000000
> -0800
> @@ -458,7 +458,7 @@
>
> if ( $inband ) {
> emit ( "run_tc qdisc add dev $device handle ffff: ingress",
> - "run_tc filter add dev $device parent ffff: protocol ip
> prio 50 u32 match ip src 0.0.0.0/0 police rate ${inband}kbit burst 10k drop
> flowid :1"
> + "run_tc filter add dev $device parent ffff: protocol ip
> prio 50 u32 match ip src 0.0.0.0/0 police rate ${inband}kbit burst 10k drop"
> );
> }
>
OK thanks.
Actually, looking a bit closer, it appears that
shorewall-perl-4.0.7.tar.bz2 from the base directory already has
patch-perl-4.0.7.1 applied, which is very confusing. From the previous
discussoin, I had understood that the point release patches were to be
applied in increasing order to the tarballs in base. Did I totally
misunderstand?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
