On Sat, Mar 15, 2008 at 01:40:41PM +0000, Felix Homann wrote: > Option 1 seemed most reasonable to me since apparently nobody feels > responsible for fixing the issue!
I cannot fix that in a reasonable way (depending upon db4.5-utils and db4.6-utils just for that isn't just an option). It's not that I don't _want_ to fix it, it's just that I cannot (in a reasonable way). > And does it make any difference? Does apt-listchanges behave very > different with a trashed history? (I really don't know, could you please > elucidate on this? ) it doesn't show changelogs for a package it considers new (as it would else show YEARS of useless changelogs since it's not really "changes"). So you won't see changelogs for upgrades on your _next_ upgrade of those packages, only for the one after that. > > the solution is to: > >$ db4.6_dump /var/lib/apt/listchanges.db | db4.5_load a.db > >$ mv a.db /var/lib/apt/listchanges.db > > Thanks, this should have gone in a NEWS file, or at least in the bug > tracking system days ago, IMO. It has been answered to many people having the problem, I was convinced I let it in the bug report as well, seems I didn't. I'm not motivated to do an upload _just_ for a modificated README.Debian (that's not really package NEWS really) for a python issue, I'm sorry. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpB4YKhnn0vZ.pgp
Description: PGP signature
