The problem occured in the Ubuntu development version, because of reverting back to db4.5 for the bsddb3 extension (from db4.6).
Sure, that's not a common case (or a bug in Debian), but it appears to me that deleting the last_seen DB is better than having no apt-listchanges reports anymore. The point here is that DB failure should get handled better by apt-listchanges: when recreating the DB is not an option, it could just exit with a more applicable error message, e.g. "The last_seen database (%s) appears to be broken. You may want to inspect the database file or remove it manually." -- http://daniel.hahler.de/
signature.asc
Description: This is a digitally signed message part.
