From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 8EA9C431FBF; Tue, 12 Jan 2010 10:33:46 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09LB+GFqwnqG; Tue, 12 Jan 2010 10:33:46 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 20967431FAE; Tue, 12 Jan 2010 10:33:46 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id CAE70550090; Tue, 12 Jan 2010 10:33:45 -0800 (PST) From: Carl Worth To: racin@free.fr, notmuch@notmuchmail.org In-Reply-To: <1478830590.12052901263166145181.JavaMail.root@zimbra1-e1.priv.proxad.net> References: <1478830590.12052901263166145181.JavaMail.root@zimbra1-e1.priv.proxad.net> Date: Tue, 12 Jan 2010 10:33:40 -0800 Message-ID: <87pr5fgol7.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Subject: Re: Bug with commit 2e96464f9705be4ec772280cad71a6c9d5831e6f X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 18:33:46 -0000 --=-=-= On Mon, 11 Jan 2010 00:29:05 +0100 (CET), racin@free.fr wrote: > 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. Hi Mathieu, Thanks for testing the new notmuch. I appreciate that. And I'm sorry to hear that you're weren't pleasantly rewarded for your efforts. I tried as well as I could to avoid bugs slipping through, but I also knew I couldn't test for everything. > I did a git bisect, which tells me the first bad commit is commit > 2e96464f9705be4ec772280cad71a6c9d5831e6f. Can you tell me what you were bisecting? Were you attempting the database upgrade over again each time? Or just testing whether you could update a post-upgraded database each time? That commit looks remarkably benign. It doesn't really change anything about how the database is interpreted or upgraded, (but merely adds a list to defer the printing of a few filenames). Could you perform a test to confirm the results of bisection---such as manually applying and reverting this patch to the immediately preceding version and check whether the behavior changes? > I did not try to use the new xapian database or to update xapian; > maybe this is the problem. It shouldn't be. The new notmuch is intended to work just fin with an old Xapian. And I *think* that I tested that at least a few times. > I will try to investigate a bit more. Thanks. I'll look forward to any further information you can provide. And if it would be practical for you to share your email database with me (privately, of course) so that I can investigate, I would be glad to do that. Obviously, I'll understand if that's not possible. Just contact me off-list if you'd like to arrange something like that. -Carl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLTMCE6JDdNq8qSWgRAo3yAJ4mzGtJk6no8IWKM17vPWalv3GCogCfa675 jVUFJ3BCk21gAXj+dhrrsfA= =TlSi -----END PGP SIGNATURE----- --=-=-=--