Bug#659474: spamassassin: sa-compile problem on upgrade
I've just gone through an upgrade from a basic squeeze installation on which sa-compile and sa-update had previously run successfully, and I don't see the behavior you're talking about. Had you enabled the cron job and run sa-compile successfully prior to the upgrade? My test system is a virtual machine on which only minimal packages were installed (e.g. nothing was selected from tasksel, and the only individual packages installed were openssh-server, spamassassin, and re2c), so it's hard to see where there might be a missing dependency. For reference, here are the relevant bits from my upgrade transcript: root@squeeze:~# apt-get install spamassassin re2c Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: binutils cpp cpp-4.4 gcc gcc-4.4 libc-dev-bin libc6-dev libdb4.7 libdigest-hmac-perl libdigest-sha1-perl liberror-perl libfont-afm-perl libgmp3c2 libgomp1 libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libio-socket-inet6-perl libmail-spf-perl libmailtools-perl libmpfr4 libnet-dns-perl libnet-ip-perl libnetaddr-ip-perl libsocket6-perl libsys-hostname-long-perl libtimedate-perl liburi-perl libwww-perl linux-libc-dev make manpages-dev perl perl-modules spamc Suggested packages: binutils-doc cpp-doc gcc-4.4-locales gcc-multilib autoconf automake1.9 libtool flex bison gdb gcc-doc gcc-4.4-multilib libmudflap0-4.4-dev gcc-4.4-doc libgcc1-dbg libgomp1-dbg libmudflap0-dbg libcloog-ppl0 libppl-c2 libppl7 glibc-doc libdata-dump-perl libcrypt-ssleay-perl libio-socket-ssl-perl make-doc perl-doc libterm-readline-gnu-perl libterm-readline-perl-perl razor libnet-ident-perl libdbi-perl pyzor libcompress-zlib-perl libmail-dkim-perl Recommended packages: libsys-syslog-perl The following NEW packages will be installed: binutils cpp cpp-4.4 gcc gcc-4.4 libc-dev-bin libc6-dev libdb4.7 libdigest-hmac-perl libdigest-sha1-perl liberror-perl libfont-afm-perl libgmp3c2 libgomp1 libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libio-socket-inet6-perl libmail-spf-perl libmailtools-perl libmpfr4 libnet-dns-perl libnet-ip-perl libnetaddr-ip-perl libsocket6-perl libsys-hostname-long-perl libtimedate-perl liburi-perl libwww-perl linux-libc-dev make manpages-dev perl perl-modules re2c spamassassin spamc 0 upgraded, 38 newly installed, 0 to remove and 0 not upgraded. Need to get 28.9 MB of archives. After this operation, 95.6 MB of additional disk space will be used. Do you want to continue [Y/n]? ... Setting up spamassassin (3.3.1-1) ... SpamAssassin Mail Filter Daemon: disabled, see /etc/default/spamassassin root@squeeze:~# sa-update -v Update available for channel updates.spamassassin.org Update was available, and was downloaded and installed successfully root@squeeze:~# sa-compile Jul 23 23:56:17.520 [5628] info: generic: base extraction starting. this can take a while... Jul 23 23:56:17.520 [5628] info: generic: extracting from rules of type body_0 100% [=] 79.64 rules/sec 00m07s DONE 100% [=] 268.94 bases/sec 00m09s DONE Jul 23 23:56:35.153 [5628] info: body_0: 1039 base strings extracted in 18 seconds cd /tmp/.spamassassin5628tyS9VGtmp cd Mail-SpamAssassin-CompiledRegexps-body_0 re2c -i -b -o scanner1.c scanner1.re re2c -i -b -o scanner2.c scanner2.re re2c -i -b -o scanner3.c scanner3.re re2c -i -b -o scanner4.c scanner4.re re2c -i -b -o scanner5.c scanner5.re re2c -i -b -o scanner6.c scanner6.re /usr/bin/perl Makefile.PL PREFIX=/tmp/.spamassassin5628tyS9VGtmp/ignored INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.010/3.003001 Writing Makefile for Mail::SpamAssassin::CompiledRegexps::body_0 make cp body_0.pm blib/lib/Mail/SpamAssassin/CompiledRegexps/body_0.pm /usr/bin/perl /usr/share/perl/5.10/ExtUtils/xsubpp -typemap /usr/share/perl/5.10/ExtUtils/typemap body_0.xs body_0.xsc mv body_0.xsc body_0.c cc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\1.0\ -DXS_VERSION=\1.0\ -fPIC -I/usr/lib/perl/5.10/CORE body_0.c cc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\1.0\ -DXS_VERSION=\1.0\ -fPIC -I/usr/lib/perl/5.10/CORE scanner1.c cc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\1.0\ -DXS_VERSION=\1.0\ -fPIC -I/usr/lib/perl/5.10/CORE scanner2.c cc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe
Bug#659474: spamassassin: sa-compile problem on upgrade
On Tue, Jul 24, 2012 at 12:19:46AM -0700, Noah Meyerhans wrote: Had you enabled the cron job and run sa-compile successfully prior to the upgrade? I don't remember. I had not touched the spamassassin setup for years. My test system is a virtual machine on which only minimal packages were installed (e.g. nothing was selected from tasksel, and the only individual packages installed were openssh-server, spamassassin, and re2c), so it's hard to see where there might be a missing dependency. As mentioned in the original report (why did you not cc the original reporter, btw?), the problem existed in between spamassassin upgrade and libc6-dev upgrade. If there was nothing holding back libc6-dev in your test apt-get upgrade (and it's likely that a minimal install would not have anything like that), the problem will not appear. If spamassassin did depend on the proper version of libc6-dev, it too would have been held back until dist-upgrade in my real-world case. $ grep -E 'spamassassin|libc9-dev' /var/log/dpkg.log 2012-07-20 15:27:03 upgrade spamassassin 3.3.1-1 3.3.2-3 2012-07-20 15:27:03 status half-configured spamassassin 3.3.1-1 2012-07-20 15:27:03 status unpacked spamassassin 3.3.1-1 2012-07-20 15:27:03 status half-installed spamassassin 3.3.1-1 2012-07-20 15:27:03 status half-installed spamassassin 3.3.1-1 2012-07-20 15:27:03 status half-installed spamassassin 3.3.1-1 2012-07-20 15:27:04 status unpacked spamassassin 3.3.2-3 2012-07-20 15:27:04 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 configure spamassassin 3.3.2-3 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status unpacked spamassassin 3.3.2-3 2012-07-20 15:29:45 status half-configured spamassassin 3.3.2-3 2012-07-20 15:49:55 configure spamassassin 3.3.2-3 3.3.2-3 2012-07-20 15:49:55 status half-configured spamassassin 3.3.2-3 2012-07-20 15:58:21 upgrade libc6-dev 2.11.3-3 2.13-33 2012-07-20 15:58:21 status half-configured libc6-dev 2.11.3-3 2012-07-20 15:58:21 status unpacked libc6-dev 2.11.3-3 2012-07-20 15:58:21 status half-installed libc6-dev 2.11.3-3 2012-07-20 15:58:23 status half-installed libc6-dev 2.11.3-3 2012-07-20 15:58:24 status unpacked libc6-dev 2.13-33 2012-07-20 15:58:24 status unpacked libc6-dev 2.13-33 2012-07-20 16:03:12 configure spamassassin:all 3.3.2-3 none 2012-07-20 16:03:12 status half-configured spamassassin:all 3.3.2-3 2012-07-20 16:04:12 status installed spamassassin:all 3.3.2-3 2012-07-20 16:04:13 configure libc6-dev:i386 2.13-33 none 2012-07-20 16:04:13 status unpacked libc6-dev:i386 2.13-33 2012-07-20 16:04:13 status half-configured libc6-dev:i386 2.13-33 2012-07-20 16:04:13 status installed libc6-dev:i386 2.13-33 2012-07-20 16:32:17 status triggers-pending spamassassin:all 3.3.2-3 2012-07-20 16:32:19 trigproc spamassassin:all 3.3.2-3 none 2012-07-20 16:32:19 status half-configured spamassassin:all 3.3.2-3 2012-07-20 16:33:37 status installed spamassassin:all 3.3.2-3 $ For reference, here are the relevant bits from my upgrade transcript: Sorry, you deleted some relevant bits: root@squeeze:~# apt-get upgrade Reading package lists... Done Building dependency tree ... 72 upgraded, 0 newly installed, 0 to remove and 116 not upgraded. What were those 72 packages? An interesting question is what would happen if instead of apt-get upgrade, you'd use apt-get install spamassassin after editing sources.list. That would likely expose the issue. (I may try this myself, in fact.) -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ signature.asc Description: Digital signature
Bug#659474: spamassassin: sa-compile problem on upgrade
severity 659474 normal thanks On Tue, Jul 24, 2012 at 11:30:25AM +0300, Antti-Juhani Kaijanaho wrote: On Tue, Jul 24, 2012 at 12:19:46AM -0700, Noah Meyerhans wrote: Had you enabled the cron job and run sa-compile successfully prior to the upgrade? I don't remember. I had not touched the spamassassin setup for years. [...] An interesting question is what would happen if instead of apt-get upgrade, you'd use apt-get install spamassassin after editing sources.list. That would likely expose the issue. (I may try this myself, in fact.) I've now completed this test. No errors detected. Okay, I think it's clear now that this is not a simple dependency problem and is unlikely to hit most upgraders. Hence downgrading back to normal. Looks like both the packaged cronjob and my handcrafted cronjob have been disabled in that system, so the data it tried to compile was probably very old. (Is there some way I could determine how old it is?) Interesting, though, that an upgrade to libc6-dev made it work. -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ signature.asc Description: Digital signature
Processed: Re: Bug#659474: spamassassin: sa-compile problem on upgrade
Processing commands for cont...@bugs.debian.org: severity 659474 normal Bug #659474 [spamassassin] spamassassin: sa-compile problem on upgrade Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 659474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
