Pierre Habouzit wrote:
Everything seems to be fine afterwards again.
of course, and you just trashed your whole history with it, nice... or
not.
Well, without knowledge of the intrinsics, I was faced with only 3 options:
1. continue using apt-listchanges but trashing the history
2. remove apt-listchanges to get rid of the error messages
3. just live with the error messages
(4. Dig into the intrinsics)
Option 1 seemed most reasonable to me since apparently nobody feels
responsible for fixing the issue!
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? )
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.
Until you find a real solution you could include this information in a
NEWS.Debian file.
Or one could instead fix python
That's what I meant "debating responsibilities": You won't fix, Matthias
won't fix ...then at least tell the user's what *they* can do to work
around this bug in the meantime.
Nevertheless, thank you very much for this better solution, I'm gonna
use it on my 2nd machine!
Kind regards,
Felix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
