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
