From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 046206DE1E85 for ; Thu, 23 Feb 2017 06:01:50 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5vN9ImZYt1d for ; Thu, 23 Feb 2017 06:01:49 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 5A6D86DE1E7D for ; Thu, 23 Feb 2017 06:01:48 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cgtxD-0003pM-7H; Thu, 23 Feb 2017 09:01:07 -0500 Received: (nullmailer pid 28827 invoked by uid 1000); Thu, 23 Feb 2017 14:01:41 -0000 From: David Bremner To: Rafael Avila de Espindola , Andy Wills , notmuch@notmuchmail.org Subject: Re: bug report In-Reply-To: <87r32p118a.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> References: <20170221203517.GD13922@andy-x200> <87poib3tef.fsf@tethera.net> <87ino24jvb.fsf@tethera.net> <87a89enswj.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> <87wpci6wxk.fsf@tesseract.cs.unb.ca> <87r32p118a.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> Date: Thu, 23 Feb 2017 10:01:41 -0400 Message-ID: <87tw7l6m62.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Thu, 23 Feb 2017 14:01:50 -0000 Rafael Avila de Espindola writes: > David Bremner writes: > >> It's hard to be sure without more details, but it sounds like a locking >> problem, which could also be be fixed by upgrading to current xapian and >> notmuch. > > I currently have notmuch-0.23.5-1.fc25.x86_64 and > xapian-core-1.2.24-1.fc25.x86_64. You need notmuch built against xapian 1.4 to fix the locking error I was thinking of. d