Hello Julien, On Fri, Apr 11, 2008 at 05:40:10PM +0200, Julien Cristau wrote: > On Fri, Apr 11, 2008 at 17:25:25 +0200, Helge Kreutzmann wrote: > > On Sat, Apr 05, 2008 at 11:00:47AM +0100, Adam D. Barratt wrote: > > > On Sat, 2008-04-05 at 09:40 +0200, Helge Kreutzmann wrote: > > > I used the version Pierre suggested in message #99, which worked fine > > > for me: > > > > > > $ db4.6_dump /var/lib/apt/listchanges.db | db4.5_load a.db > > > $ mv a.db /var/lib/apt/listchanges.db > > > > This worked for me as well. IMHO this should be done in the package > > automatically if it detectes a broken version .... > > > There's no guarantee that db4.5-util and db4.6-util are installed (and > no, making apt-listchanges depend on those two packages is not an > option).
For me, in order of preference:
a) Automatic fix without the user noticing (which you ruled out, ok)
b) Providing a script essentially running the commands, and telling
the user prominently if apt-listchanges detects a broken db about
this script (and its extra requirements, which the script in theory
could call in, if so desired)
c) A prominent note with by apt-debconf (i.e. error message) telling
the user the fix, preferrably translatable
d) A prominent note in NEWS.Debian informing about the problem and its
fix
e) A note in README.Debian informing about this problem and its fix
Greetings
Helge
P.S. Are people directly upgrading from Etch affected as well?
--
Dr. Helge Kreutzmann [EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
