SpamAssassin 3.0.1 was released, see URL. New ebuild follows, the announcement: SpamAssassin 3.0.1 is released! 3.0.1 contains some important bugfixes, and is recommended. Highlights: - excessive memory-usage fixes - bug fixed which stopped DCC, Pyzor working with amavisd - deprecate RCVD_IN_RFC_IPWHOIS - user_prefs were staying active between different spamd users, fixed - user_prefs blacklist entries were not working in spamd, fixed - excessive time and memory consumption when ok_languages is used, fixed - sa-learn -u switch to specify the username for virtual environments - avoid bug in Sys::Hostname::Long that renames the hostname when "make test" is run - whitelist the top 125 queried SURBL domains common in nonspam Pick it up at http://spamassassin.apache.org/ ! md5sum of archive files: 83f60f97c823d9b8df19309247fe33eb Mail-SpamAssassin-3.0.1.tar.bz2 759e0486b07c4a03aa340d4a04e1d849 Mail-SpamAssassin-3.0.1.tar.gz e42d4f6b7228f899efdfdce03b8851a0 Mail-SpamAssassin-3.0.1.zip sha1sum of archive files: 7ad929efc388ebdf26da052c6fca958c7541bb4f Mail-SpamAssassin-3.0.1.tar.bz2 a3aebae1bf3c97830e540c42dc64791787d966c9 Mail-SpamAssassin-3.0.1.tar.gz e4f23ad8251914bb240a4e42438310a263ca5056 Mail-SpamAssassin-3.0.1.zip The release files also have a .asc accompanying them. The file serves as an external GPG signature for the given release file. The signing key is available via the wwwkeys.pgp.net key server, as well as http://spamassassin.apache.org/released/GPG-SIGNING-KEY The key information is: pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@spamassassin.org> Key fingerprint =3D 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B
Created attachment 42565 [details] spamassassin-3.0.1.ebuild The changes in this ebuild: --- /usr/portage/mail-filter/spamassassin/spamassassin-3.0.0-r1.ebuild 2004-10-16 16:09:45.000000000 +0200 +++ spamassassin-3.0.1.ebuild 2004-10-17 22:08:26.000000000 +0200 @@ -19,6 +19,7 @@ DEPEND=">=dev-lang/perl-5.8.2-r1 >=dev-perl/PodParser-1.22 + dev-perl/MIME-Base64 >=dev-perl/HTML-Parser-3.31 >=dev-perl/Net-DNS-0.34 dev-perl/Digest-SHA1 @@ -98,7 +99,7 @@ src_compile() { # Add Gentoo tag to make it easier for the upstream devs to spot # possible modifications or patches. - version_tag="g${PV/*_/}${PR/r0/}" + version_tag="g${PV:6}${PR}" version_str="${PV//_/-}-${version_tag}" # Create the Gentoo config file before Makefile.PL is called so it @@ -158,6 +159,7 @@ fperms 755 /etc/init.d/spamd insinto /etc/conf.d newins ${FILESDIR}/3.0.0-spamd.conf spamd + dosym /etc/mail/spamassassin /etc/spamassassin if use doc; then dodoc spamd/PROTOCOL @@ -176,12 +178,13 @@ fi if has_version "mail-filter/razor"; then - if ! has_version "<=net-mail/razor-2.40"; then + if ! has_version ">=mail-filter/razor-2.61"; then ewarn "You have $(best_version mail-filter/razor) installed but SpamAssassin" - ewarn "requires at least version 2.40, version 2.61 or later is recommended." - elif ! has_version ">=net-mail/razor-2.61"; then - ewarn "You have $(best_version mail-filter/razor) installed but SpamAssassin" - ewarn "recommends at least version 2.61." + if has_version "<mail-filter/razor-2.40"; then + ewarn "requires at least version 2.40, version 2.61 or later is recommended." + else + ewarn "recommends at least version 2.61." + fi fi fi
That last block doesn't make sense... if you don't have a version <=2.40, warn them that it requires >=2.40...?
/me will be taking donations for reading classes and babysitters. Hold on, about to test and hit portage with it :)
Posted. :)
When will SpamAss 3.0 or 3.0.1 be as stable in portage? They have been available for some time already. Thanx!
I hope 3.0 won't _ever_ be marked stable, since it has some awful memory leaks. As for 3.0.1, it will get stable once we decide it's ok to mark it stable, just as any other package. Add it to your /etc/portage/package.keywords if you do not wish to wait. As 3.0.1 is in portage, I suggest closing this bug. Michael?
I recommend that you don't mark SpamAssassin 3 stable before it hits the 3.0.2 mark. 3.0.0 has the noted memory issues and there are still known problems in 3.0.1 which are being worked on. It's not that 3.0.1 will eat you boxes and your children, it's very reliable, but everybody who wants to use it can enable it in his profile.keywords and can't blame Gentoo then if something goes wrong :) Closing this bug as the ebuild is in the tree.
