Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Damien Wyart
Sorry to break the thread, I had not subscribed to the bug (done now).

Did a quick test of applying Dominique's suggestion on top of
libnetaddr-ip-perl v4.035, and this doesn't seem to solve the problem
with spamassassin. The message with lead to creation of 601601 is still
appearing.

Please not I am not a Perl expert, so my test might not be highly
reliable but this gives a hint...


Best,

-- 
Damien



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Nicholas Bamber
Damian,   Sorry I should have made myself clearer. I was not suggesting 
that Dominique's idea would help - except as very, very long shot. 
Rather We have two bugs in assassin that have at sometime implicated 
NetAddr::IP. #517361 is a separate bug
but at present I cannot investigate further without help from people who 
know spamassasin. Obviously it is spamassasin's interests to squash as 
many NetAddr::IP bugs as possible. So I am suggesting that someone using 
spamassasin helps me test Dominuque's idea and I react proactively to 
any NetAddr::IP issues.


Damien Wyart wrote:

Sorry to break the thread, I had not subscribed to the bug (done now).

Did a quick test of applying Dominique's suggestion on top of
libnetaddr-ip-perl v4.035, and this doesn't seem to solve the problem
with spamassassin. The message with lead to creation of 601601 is still
appearing.

Please not I am not a Perl expert, so my test might not be highly
reliable but this gives a hint...


Best,

  





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Damien Wyart
Ok, no problem. Thanks for your explanation.

As the last message in 601601 was refering to 517361, I thought there
was a technical link between the two.

So let's hope some SA hackers will be able to help on these two
issues...


Best,

Damien



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Noah Meyerhans
On Tue, Nov 02, 2010 at 10:11:32AM +, Nicholas Bamber wrote:
 Damian,   Sorry I should have made myself clearer. I was not suggesting  
 that Dominique's idea would help - except as very, very long shot.  
 Rather We have two bugs in assassin that have at sometime implicated  
 NetAddr::IP. #517361 is a separate bug
 but at present I cannot investigate further without help from people who  
 know spamassasin. Obviously it is spamassasin's interests to squash as  
 many NetAddr::IP bugs as possible. So I am suggesting that someone using  
 spamassasin helps me test Dominuque's idea and I react proactively to  
 any NetAddr::IP issues.

Please refer to a previous update that I made to this bug. [1]  That
message contains a small program, as well as sample correct and
incorrect output.  That program is essentially the part of spamassassin
that is generating warnings based on the change in behavior observed in
NetAddr::IP.

noah

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601601#37



signature.asc
Description: Digital signature


Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Nicholas Bamber

Damian,
   I know you tied Noah's test.pl script with your own 4.035 build and 
it failed. Could try it with the official 4.035 build? It works for me 
and Elimar. The original problem still persisted for Elimar however.



Noah Meyerhans wrote:

On Tue, Nov 02, 2010 at 10:11:32AM +, Nicholas Bamber wrote:
  
Damian,   Sorry I should have made myself clearer. I was not suggesting  
that Dominique's idea would help - except as very, very long shot.  
Rather We have two bugs in assassin that have at sometime implicated  
NetAddr::IP. #517361 is a separate bug
but at present I cannot investigate further without help from people who  
know spamassasin. Obviously it is spamassasin's interests to squash as  
many NetAddr::IP bugs as possible. So I am suggesting that someone using  
spamassasin helps me test Dominuque's idea and I react proactively to  
any NetAddr::IP issues.



Please refer to a previous update that I made to this bug. [1]  That
message contains a small program, as well as sample correct and
incorrect output.  That program is essentially the part of spamassassin
that is generating warnings based on the change in behavior observed in
NetAddr::IP.

noah

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601601#37

  





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-11-02 Thread Damien Wyart
What was wrong with my own 4.035 build was SpamAssassin's behaviour
(this is what I wrote in my reports, msgs 59 and 64), NOT Noah's test.pl
script. The test script was OK, but from the start I have wanted to
highlight that the SA problem, at the origin of 601601, was still there,
so the test and its associated patch in 4.035 were not enough concerning
601601.

With 4.035 (my build or the official one), I still see the problematic
messages from SA when starting, learning or when the daily cron runs.
But the test.pl script if fine.

So I am in the same situation as Elimar.

-- 
Damien Wyart



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-10-31 Thread Elimar Riesebieter
Package: libnetaddr-ip-perl
Version: 4.035+dfsg-1
Severity: normal


The bug still persists:

r...@baumbart /etc/default # /usr/sbin/amavisd-new-cronjob sa-sync
netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included
netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included

Elimar

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.35.7-baumbart (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages libnetaddr-ip-perl depends on:
ii  libc6 2.11.2-6   Embedded GNU C Library: Shared lib
ii  perl  5.10.1-15  Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.10.1]5.10.1-15  minimal Perl system

libnetaddr-ip-perl recommends no packages.

libnetaddr-ip-perl suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-10-31 Thread Nicholas Bamber

Elimar

Please could you download Noah's test script and post us the result. It 
was his work that isolated the problem down to the NetAddr::IP module so 
we really need to start from that point.


http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;filename=test.pl;att=1;bug=601601



Elimar Riesebieter wrote:

Package: libnetaddr-ip-perl
Version: 4.035+dfsg-1
Severity: normal


The bug still persists:

r...@baumbart /etc/default # /usr/sbin/amavisd-new-cronjob sa-sync
netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included
netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included

Elimar

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.35.7-baumbart (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages libnetaddr-ip-perl depends on:
ii  libc6 2.11.2-6   Embedded GNU C Library: Shared lib
ii  perl  5.10.1-15  Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.10.1]5.10.1-15  minimal Perl system


libnetaddr-ip-perl recommends no packages.

libnetaddr-ip-perl suggests no packages.

-- no debconf information


  





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-10-31 Thread Elimar Riesebieter
* Nicholas Bamber [101031 18:54 +]:
 Elimar
 
 Please could you download Noah's test script and post us the result. It was
 his work that isolated the problem down to the NetAddr::IP module so we
 really need to start from that point.
 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;filename=test.pl;att=1;bug=601601
 

Here we go:

r...@baumbart ~ # perl test.pl
Loopback network: 127.0.0.0/8
converted to v6 mapped: 0:0:0:0:0::7F00:0/104
IPv6 loopback address: 0:0:0:0:0:0:0:1/128
Is 0:0:0:0:0:0:0:1/128 contained within 0:0:0:0:0::7F00:0/104? 0

Elimar

-- 
  The path to source is always uphill!
-unknown-


signature.asc
Description: Digital signature


Bug#601601: libnetaddr-ip-perl: Reopen

2010-10-31 Thread Nicholas Bamber

Elimar,
   Thanks for the fast response. Based upon this I will pass the ticket 
back to the spamassassin package.


Elimar Riesebieter wrote:

* Nicholas Bamber [101031 18:54 +]:
  

Elimar

Please could you download Noah's test script and post us the result. It was
his work that isolated the problem down to the NetAddr::IP module so we
really need to start from that point.

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;filename=test.pl;att=1;bug=601601




Here we go:

r...@baumbart ~ # perl test.pl
Loopback network: 127.0.0.0/8
converted to v6 mapped: 0:0:0:0:0::7F00:0/104
IPv6 loopback address: 0:0:0:0:0:0:0:1/128
Is 0:0:0:0:0:0:0:1/128 contained within 0:0:0:0:0::7F00:0/104? 0

Elimar

  





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601601: libnetaddr-ip-perl: Reopen

2010-10-31 Thread Nicholas Bamber
Actually if someone is willing to test it in spamassasin I am willing to 
put a patched version of NetAddr::IP in experimental to try out 
Dominique's suggestion on 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517361.  Obviously if 
that works I will forward the patch upstream.


Nicholas Bamber wrote:

Elimar,
   Thanks for the fast response. Based upon this I will pass the 
ticket back to the spamassassin package.


Elimar Riesebieter wrote:

* Nicholas Bamber [101031 18:54 +]:
 

Elimar

Please could you download Noah's test script and post us the result. 
It was

his work that isolated the problem down to the NetAddr::IP module so we
really need to start from that point.

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;filename=test.pl;att=1;bug=601601 






Here we go:

r...@baumbart ~ # perl test.pl
Loopback network: 127.0.0.0/8
converted to v6 mapped: 0:0:0:0:0::7F00:0/104
IPv6 loopback address: 0:0:0:0:0:0:0:1/128
Is 0:0:0:0:0:0:0:1/128 contained within 0:0:0:0:0::7F00:0/104? 0

Elimar

  





___
pkg-perl-maintainers mailing list
pkg-perl-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-perl-maintainers





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org