Your message dated Wed, 13 Jun 2007 06:32:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427862: fixed in spamassassin 3.2.1-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: spamassassin
Version: 3.2.0-2
Severity: normal
The docs are not really clear on how sa-compile is integrated with the
rest of the package. After reading them I was left wondering:
1. Will a compiled ruleset prevent an upgraded ruleset from being seen?
I see that the compiled ruleset is put in a versioned directory in
/var, but I'm unsure that would happen if a rule was changed w/o the
upstream version changing.
2. If I enable the cron job, will it compile the ruleset every day for
me? (I read the code and found it does, although it also /dev/nulls any
errors, which I don't like.)
3. What do I need to do on upgrade? Apparently the postinst does not run
sa-compile, so it seems I'd need remember to run sa-compile by hand
unless I enable the cron job. IMHO, it would be good to run
sa-compile in the postinst if re2c is available and
/var/lib/spamassassin/compiled exists.
BTW, the README.Debian has some old text about sa-update being manual
and "quite new", which seems outdated now that there's a cron job.
Thanks for your work in integrating these new features into
the spamassassin package.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-2-xen-k7 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages spamassassin depends on:
ii libarchive-tar-perl 1.31-1 Archive::Tar - manipulate tar file
ii libdigest-sha1-perl 2.11-2 NIST SHA-1 message digest algorith
ii libhtml-parser-perl 3.56-1 A collection of modules that parse
ii libio-zlib-perl 1.04-1 IO:: style interface to Compress::
ii libnet-dns-perl 0.59-1 Perform DNS queries from a Perl sc
ii libsocket6-perl 0.19-1 Perl extensions for IPv6
ii libsys-hostname-long-perl 1.4-1 Figure out the long (fully-qualifi
ii libwww-perl 5.805-1 WWW client/server library for Perl
ii perl 5.8.8-7 Larry Wall's Practical Extraction
Versions of packages spamassassin recommends:
ii gnupg 1.4.6-2 GNU privacy guard - a free PGP rep
pn libmail-spf-query-perl <none> (no description available)
pn libsys-syslog-perl <none> (no description available)
ii re2c 0.12.1-1 tool for generating fast C-based r
pn spamc <none> (no description available)
-- no debconf information
--
see shy jo
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.2.1-1
We believe that the bug you reported is fixed in the latest version of
spamassassin, which is due to be installed in the Debian FTP archive:
spamassassin_3.2.1-1.diff.gz
to pool/main/s/spamassassin/spamassassin_3.2.1-1.diff.gz
spamassassin_3.2.1-1.dsc
to pool/main/s/spamassassin/spamassassin_3.2.1-1.dsc
spamassassin_3.2.1-1_all.deb
to pool/main/s/spamassassin/spamassassin_3.2.1-1_all.deb
spamassassin_3.2.1.orig.tar.gz
to pool/main/s/spamassassin/spamassassin_3.2.1.orig.tar.gz
spamc_3.2.1-1_i386.deb
to pool/main/s/spamassassin/spamc_3.2.1-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Duncan Findlay <[EMAIL PROTECTED]> (supplier of updated spamassassin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 11 Jun 2007 14:36:38 -0700
Source: spamassassin
Binary: spamassassin spamc
Architecture: source all i386
Version: 3.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Duncan Findlay <[EMAIL PROTECTED]>
Changed-By: Duncan Findlay <[EMAIL PROTECTED]>
Description:
spamassassin - Perl-based spam filter using text analysis
spamc - Client for SpamAssassin spam filtering daemon
Closes: 402241 425685 427725 427862 428316
Changes:
spamassassin (3.2.1-1) unstable; urgency=low
.
* New upstream release
- Fixes security vulnerability CVE-2007-2873
- Silences loud warning message (Closes: #425685)
- Properly document message size "limit" (Closes: #402241)
* Recommends: gcc, libc6-dev, make for sa-compile (Closes: #427725)
* Fixed out of date section in README.Debian discussing sa-update
(Closes: #428316)
* Clarified how sa-compile works in README.Debian (Closes: #427862)
* Check in cron.daily that /var/lib/spamassassin/compiled exists
(i.e. only compile rules if sa-compile has previously been run)
* Recompile rules in postinst if /var/lib/spamassassin/compiled
exists (and sa-update and re2c exist)
Files:
d0be7be0de4a87317f38dbd30f6b5ef9 765 mail optional spamassassin_3.2.1-1.dsc
a7d51294c565999da01f212e5ad2a031 1193561 mail optional
spamassassin_3.2.1.orig.tar.gz
9c50ffa91e440e70f660fb3724e0e177 33739 mail optional
spamassassin_3.2.1-1.diff.gz
5ec799c1221eca5b4311f256f2d4cb34 1062164 mail optional
spamassassin_3.2.1-1_all.deb
f6561f095e21ca010f753822efbe4c07 67252 mail optional spamc_3.2.1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGb4mmqjUzNGvmnNARAq0aAJ99yf/GZREE4XGR1rrmr3bpVCFiVgCgiIZr
R4JesHGBwotW8iyDIq6IGqM=
=f7rO
-----END PGP SIGNATURE-----
--- End Message ---
