Hey good people-- I got bit by this bug, and fixed it with:
aptitude install db4.6-util db4.5-util
TMPDB=$(mktemp -d)/listchanges.db
db4.6_dump /var/lib/apt/listchanges.db | db4.5_load "$TMPDB"
ln /var/lib/apt/listchanges.db /var/lib/apt/listchanges.db.old
mv "$TMPDB" /var/lib/apt/listchanges.db
I know this problem isn't technically the fault of apt-listchanges,
but it would be a politeness to handle this failure more gracefully
than apt-listchanges currently does.
For example, if the "bsddb.db.DBRunRecoveryError" pops up,
apt-listchanges could see if the version of python is the one with the
older db4.5. If db4.5-util and db4.6-util are present, it could offer
to repair the database (using Pierre's technique [0], which worked for
me as i describe above). If those tools aren't available,
apt-listchanges could give a cleaner error message describing the
problem.
Not everyone who runs into this bug is going to take the time to sift
through the dozens of followups here to extract the relevant two lines
From Pierre's message, or to know what to do with them if the relevant
packages aren't installed.
Thanks for maintaining this package. It's one of the main ways that i
keep track of what's going on in the systems where i track a lot of
updates.
Regards,
--dkg
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469221#99
pgpULIeqPHuH8.pgp
Description: PGP signature
