Your message dated Sun, 21 Sep 2014 21:05:29 +0200 with message-id <[email protected]> and subject line Re: Bug#745303: need more information has caused the Debian Bug report #745303, regarding notmuch new corrupts database throwing 'Xapian::DatabaseCorruptError' to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 745303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745303 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: notmuch Version: 0.17-5+b1 Severity: normal Dear Maintainer, I'm using an offlineimap postsynchook to index my mail with `notmuch new`. Twice this week, the following error was thrown: Hook stderr:terminate called after throwing an instance of 'Xapian::DatabaseCorruptError' /home/poliveira/bin/index-mail: line 2: 7613 Aborted notmuch new Afterwards, running `notmuch new` produces the following output: notmuch new Welcome to a new version of notmuch! Your database will now be upgraded. Your notmuch database has now been upgraded to database format version 1. A Xapian exception occurred adding message: No termlist for document 70352. Error: A Xapian exception occurred. Halting processing. Processed 1 file in almost no time. No new mail. Note: A fatal error was encountered: A Xapian exception occurred Yet notmuch was not recently updated on my system. All further notmuch commands fail with: notmuch search tag:spam terminate called after throwing an instance of 'Xapian::DatabaseCorruptError' Aborted To restore a working system I must dump notmuch tags, reindex all my mail, and restore the tags. (Which is pretty long, since I keep a large amount of mails). Apart from notmuch, two other clients access the notmuch database: * emacs-notmuch * afew (9744c18c) Thanks, Pablo *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages notmuch depends on: ii libc6 2.18-4 ii libglib2.0-0 2.40.0-2 ii libgmime-2.6-0 2.6.19-3 ii libnotmuch3 0.17-5+b1 ii libtalloc2 2.1.0-1 Versions of packages notmuch recommends: ii gnupg-agent 2.0.22-3 ii notmuch-emacs 0.17-5 notmuch suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Pablo Oliveira <[email protected]> writes: > > No I have not experienced the bug recently. > But since the report, I have updated my system and I'm now running notmuch > 0.18.1. > OK, I'll close the bug for now. If it reoccurs of course please re-open the bug. Cheers, David
--- End Message ---
