On Thu, Apr 19, 2007 at 10:50:59PM +0200, Mi wrote:
> After upgrading Perl to 5.8.8 AND downgrading (!) libnet-perl from 1.20 to 
> 1.19, the problem seems to be gone.

The state of this bug seems to be a little confusing to me.

libnet-perl 1.20 was never in Debian, the latest version we had was
1.19 and it's only available in oldstable (sarge).  It's now in
perl-modules (since 5.8.0-7?).

It was originally reported against amavisd-new 1:2.4.2-6.1 which is the
version in sarge, and sarge has perl version 5.8.8-7.

The version of perl this was then reported against was 5.8.8-7, which
seems to have version 1.19 in it as far as I can see.  It also says that
upgrading to 5.8.8 solved it, so I have to wonder from which version
to which version that was.

This all seems to contradict each other.

Can someone please lists the combinations of Debian packages and
versions that either have the problem, or don't have the problem?


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to