On Fri, Nov 14, 2014 at 01:53:10PM +0100, Thijs Kinkhorst wrote:
> > I am not interested in playing bug ping-pong with the libnet-dns-perl
> > maintainers, though this bug lies with that package. It has already been
> > fixed upstream and in unstable.
> 
> No, I don't think the problem is in libnet-dns-perl but in spamassassin.
> SA uses a fragile and inappropriate way to compare version numbers. It's
> now triggered by this specific libnet-dns-perl version, but package
> maintainers should be allowed to use any valid version number for their
> packages.

Agreed, where "valid version number" is defined as something that can be
manipulated with arithmetic operators.

> As Damyan said, it can be fixed easily in SA in a robust manner:

It can be fixed in Debian by simply removing the check, since it will
always pass since (at least) oldstable. But I am not interested in a
Debian-specific workaround. If you believe this needs to be fixed in SA,
please convince upstream. I'm not interested in deviating from
upstream's decision that this isn't an SA issue.

> > If we want to release jessie without this bug in it, then we need to get
> > libnet-dns-perl 0.81 into the release.
> 
> Because of the freeze, it's not currently a reasonable request to the RT
> to unblock new upstream releases. Besides, it would only fix this concrete
> occurrence but not the root cause of fragile version number comparison.

#767750

noah

Attachment: signature.asc
Description: Digital signature

Reply via email to