Because I thought that the error with the "numeric" is totally clear, I changed the value of the new installed
perl-Archive-Tar in /usr/lib/perl5/vendor_perl/5.8.8/Archive/Tar.pm
from
$VERSION = "1.39_01";
to
$VERSION = "1.3901";
now sa-update seems to run fine.
I think I will open a bug in centos buglist.
If anybody has a correct solution please let me know.
I see the same issue. I'm not sure whether perl-Archive-Tar (package from CentOS) or SpamAssassin (package from ART) is at fault here. Any idea, Scott?
BruceLee wrote:Because I thought that the error with the "numeric" is totally clear, I changed the value of the new installed
perl-Archive-Tar in /usr/lib/perl5/vendor_perl/5.8.8/Archive/Tar.pm
from
$VERSION = "1.39_01";
to
$VERSION = "1.3901";
now sa-update seems to run fine.
I think I will open a bug in centos buglist.
If anybody has a correct solution please let me know.
And I will use it instead of changing it for this reason:
With that trick MakeMaker will only read the first line and thus read the underscore, while the perl interpreter will evaluate the $VERSION and convert the string into a number. Later operations that treat $VERSION as a number will then be able to do so without provoking a warning about $VERSION not being a number.
I'm very impressed with your detective work and your fix. Thank you.
This will undoubtedly save hours of pain for me and many others.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
I'm now getting this in Centos 4 (not 5) after updating to perl-Archive-Tar-1.39.1-1.el4_8.1 on several machines.
Most mysterious - my Tar.pm dates from 2008. I'm checking to see if I'm looking in the wrong place and will report back.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
Well, irrespective of file datestamp, it has been updated
So for Centos 4 / EL4, you'll find it in /usr/lib/perl5/vendor_perl/5.8.5/Archive/Tar.pm and you can resolve the problem in the same way.
Incidentally if you happen to use the rpmforge versions then you'll already be on 1.4.x and it doesn't have this problem.
EDIT: Incidentally, this problem may only crop up if you have enabled the centosplus repo, which I think provides a different Perl version to the base. Not sure though. Just mentioning it in case.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
We don't use CentOS Plus. That perl-Archive-Tar package is just the plain CentOS package. I'm still not sure whether perl-Archive-Tar needs a fix or is SpamAssassin needs a fix and shouldn't try to parse the version number like it currently does.
Given that 3.3.x is available, I doubt that we are we likely to get an update to 3.2.x, even if we are only talking about the sa-update component.
I don't feel like upgrading to 3.3 yet. Too many things changed, and I don't even know if qmail-scanner is compatible with it.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
Official Red Hat (and CentOS) perl-Archive-Tar updates that fix this problem are now available. Thanks to Scott for providing a fixed perl-Archive-Tar package in the Atomic repository in the meantime.