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/

Attachment: signature.asc
Description: Digital signature

Reply via email to