Am Mittwoch, den 18.01.2006, 15:17 -0500 schrieb Clint Adams: > > Set to grave, because data loss is possible. If I missed something, I > > had to do, please tell me what. README.Deian tells nothing. > > Check NEWS.Debian.
NEWS.Debian contains information for bogofilter upgrade to version >= 0.93.1-2 and it does not help, because no entry will show up when updating from <= 1.0.1-1 to >= 1.0.1-2. So as long as you do not always add a new entry when you update the BDB version your NEWS.Debian does not help anybody, and nobody will have a chance to prepare for the BDB update and a recovery as described in section 3.2.3 becomes necessary. There is no chance to repair the databases [1] with - dump the wordlists and reload them from the dump - use db4.4_upgrade - use any --recover.. option I tried them all and I did a long search for "what to do now". This is a grave bug which can be worked around by informing the user about BDB update - I agree, that an automatic preparation is maybe impossible. So please: -> add a dialog to preinst, which (in the ideal case) handles all cases described in section 2.6 in README.db and so shows an info about the necessary steps to do (see section 2.6) when updating from any version <= 1.0.1-1 to a version >= 1.0.1-2 (and do the same for later BDB updates) and maybe additionally -> add an entry to NEWS.Debian for those who use apt-listchanges [1] I use transactional databases. I don't know if non-transactional databases can be repaired this way. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
