Mailing List Archive

At 12:01 AM 3/15/04 +0100, Jim Knuth wrote:
>Hallo und guten Abend spamassassin-users,
>
>I have updated SA 2.63 => 3.0.0.


Correction. you have updated SA 2.63 to a 3.0.0 development snapshot. There
is no 3.0.0 official release yet.


>Since comes an error while sa-learn work.
>--snip
>server1:~# sa-learn --ham /var/maild/web12p1/Maildir/*
>Use of inherited AUTOLOAD for non-method Digest::SHA1::sha1_hex() is
>deprecated at /usr/local/share/perl/5.6.1/Mail/SpamAssassin/SHA1.pm line 67.
>Learned from 0 message(s) (1 message(s) examined).
>Can't locate auto/Digest/SHA1/sha1_hex.al in @INC (@INC contains: lib
>/usr/local/share/perl/5.6.1 /usr/local/lib/perl/5.6.1 /usr/lib/perl5
>/usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1
>/usr/local/lib/site_perl) at
>/usr/local/share/perl/5.6.1/Mail/SpamAssassin/SHA1.pm line 67
>--snap
>What means this? Thank you.

It could mean one of many things. The most likely things I can think of are:

1) 3.0.0 requires a different version of Digest::SHA1 than you have
2) The particular daily CVS image you downloaded is broken
(unlikely, but it _does_ happen sometimes. Particularly if it's some sneaky
perl-version specific bug that doesn't happen on the versions of perl being
used by the developers that tested the patch)

Since it's not officially released, I'd suggest waiting a few days and
downloading a newer daily snapshot and see if it's fixed. If it's not
fixed, check the bugzilla for open bugs on the issue. If there's no
reported bug, open one, and to try to narrow down the causes and symptoms
to the best of your abilities.

If this kind of uncertainty is not comfortable to you, I'd suggest staying
away from the CVS snapshot images, and work with official releases. Of
course, you can always download CVS builds to test, etc, but do keep in
mind you're playing with a version that is somewhat in-flux. 99% of the
time the CVS builds work well, as patches are reviewed prior to application
to the tree, but it's not always stable on all perl versions, etc.

Hallo und guten Morgen Matt,

danke für die Email vom 15.03.2004 um 06:17
Matt Kettler schrieb - wrote:

> Correction. you have updated SA 2.63 to a 3.0.0 development snapshot. There
> is no 3.0.0 official release yet.

right ;-)

> 1) 3.0.0 requires a different version of Digest::SHA1 than you have

I think, it`s probably possibility. What can I do?

> 2) The particular daily CVS image you downloaded is broken

no, I think it`s not so. I have downloaded 2 different versions. As *.zip and as *.tar.gz. The code in SHA1.pm ( Line 67 ) is the same.

> Since it's not officially released, I'd suggest waiting a few days and
> downloading a newer daily snapshot and see if it's fixed.

How can I see when came a new snapshot? Every night?

--
Viele Grüße, Kind regards,
Jim Knuth
jk@jkart.de
----------
Zufalls-Zitat
----------
Der Unterschied zwischen dem richtigen Wort und dem beinahe richtigen ist derselbe wie zwischen dem Blitz und dem Glühwürmchen. [Mark Twain]
----------
Dieser Text hat nichts mit dem Empfänger der Mail zu tun
----------

virengeprüft mit NOD32 Version 1.665 Update 14.03.2004

At 07:30 AM 3/15/04 +0100, Jim Knuth wrote:
>Hallo und guten Morgen Matt,
>
>danke für die Email vom 15.03.2004 um 06:17
>Matt Kettler schrieb - wrote:
>
> > Correction. you have updated SA 2.63 to a 3.0.0 development snapshot. There
> > is no 3.0.0 official release yet.
>
>right ;-)
>
> > 1) 3.0.0 requires a different version of Digest::SHA1 than you
> have
>
>I think, it`s probably possibility. What can I do?

Check CPAN for a newer version, it's the quickest way I can think of.

perl -MCPAN -e shell
install Digest::SHA1

Note: this will install the "real" Digest::SHA1, which SA will prefer over
the one that comes in SA's own code. It will likely fix your problem one
way or another.


> > 2) The particular daily CVS image you downloaded is broken
>
>no, I think it`s not so. I have downloaded 2 different versions. As *.zip
>and as *.tar.gz. The code in SHA1.pm ( Line 67 ) is the same.

Are you sure they are different versions? Or just different packaging of
the same version?

The daily CVS is built in both formats at the same time.


> > Since it's not officially released, I'd suggest waiting a few days and
> > downloading a newer daily snapshot and see if it's fixed.
>
>How can I see when came a new snapshot? Every night?

Yes, a new .tar.gz and a new .zip is built daily.

Hallo und guten Abend Matt,

danke für die Email vom 15.03.2004 um 06:17
Matt Kettler schrieb - wrote:

> It could mean one of many things. The most likely things I can think of are:

> 1) 3.0.0 requires a different version of Digest::SHA1 than you have
> 2) The particular daily CVS image you downloaded is broken
> (unlikely, but it _does_ happen sometimes. Particularly if it's some sneaky
> perl-version specific bug that doesn't happen on the versions of perl being
> used by the developers that tested the patch)

> Since it's not officially released, I'd suggest waiting a few days and
> downloading a newer daily snapshot and see if it's fixed. If it's not
> fixed, check the bugzilla for open bugs on the issue. If there's no
> reported bug, open one, and to try to narrow down the causes and symptoms
> to the best of your abilities.

> If this kind of uncertainty is not comfortable to you, I'd suggest staying
> away from the CVS snapshot images, and work with official releases. Of
> course, you can always download CVS builds to test, etc, but do keep in
> mind you're playing with a version that is somewhat in-flux. 99% of the
> time the CVS builds work well, as patches are reviewed prior to application
> to the tree, but it's not always stable on all perl versions, etc.

I´ve force install SHA1 over CPAN and new snapshot. It`s the same error. :-( Any hints?

--
Viele Grüße, Kind regards,
Jim Knuth
jk@jkart.de
----------
Zufalls-Zitat
----------
Das Buch ist die Axt für das gefrorene Meer in uns.
(Franz Kafka)
----------
Dieser Text hat nichts mit dem Empfänger der Mail zu tun
----------

virengeprüft mit NOD32 Version 1.668 Update 15.03.2004

At 09:50 PM 3/15/04 +0100, Jim Knuth wrote:
>IŽve force install SHA1 over CPAN and new snapshot. It`s the same error.
>:-( Any hints? \

Force install? erk. Why'd you do a force, that's generally a very bad thing
unless you know for certain cpan is just missing something in a strange config.