18 Sep
2006
18 Sep
'06
08:28
On Saturday 16 September 2006 22:41, John Andersen wrote:
WTF?
Try my usual technique, which is to stop zmd with 'rczmd stop', remove /var/lib/zmd/zmd.db (I think) (move it somewhere rather than just deleting it completely, in case you want to restore it ...), then restart zmd. The database is then rebuilt (you might need your installation media present at this point), and the updater starts working again. I think the updater front end should perhaps have a handler which catches this exception, and pops up a dialogue box which says "Database corrupted. Try to rebuild the database automatically?" Perhaps this would no longer be necessary with the latest updates to the update stack - I expect there are no remaining bugs ;)