Re: Bug with commit 2e96464f9705be4ec772280cad71a6c9d5831e6f

[Ali Polatel <alip@exherbo.org>]

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Ali Polatel yazmış:
> racin@free.fr yazmış:
> > Hello,
> > 
> > I just updated notmuch and now notmuch new cannot update my mail anymore... It tells me that there are
> > 700 files found, but tells that there's no new mail.
> > 
> > I did a git bisect, which tells me the first bad commit is commit 2e96464f9705be4ec772280cad71a6c9d5831e6f.
> > 
> > I did not try to use the new xapian database or to update xapian; maybe this is the problem.
> > 
> > I tested with several tools to get mail in the maildir format, including mb2md and getmail, and I always get the problem.
> Same problem here, I tried upgrading xapian to xapian-core-1.1.3_svn13824, the problem persists.
> Here's what happens here:
> 3074 alip@harikalardiyari> rm -fr .maildir/.notmuch
> 3075 alip@harikalardiyari> notmuch new
> Found 210302 total files (that's not much mail).
> No new mail.
> 3076 alip@harikalardiyari> notmuch search from:alip@exherbo.org
> 3077 alip@harikalardiyari>
> 

After doing git bisect which gave random results and testing notmuch
using cworth's notmuch-test script on another file system I figured out
my problem was due to file system corruption.
Sorry for the noise...

-- 
Regards,
Ali Polatel

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]