From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 839A61F51C;
	Wed, 30 May 2018 11:57:19 +0000 (UTC)
Date: Wed, 30 May 2018 11:57:19 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 0/4] test fixes for latest CPAN modules
Message-ID: <20180530115719.GA17038@dcvr>
References: <20180511192018.6432-1-e@80x24.org>
 <a396f48f-1e59-cbbc-17fa-53ff9c8c4b2f@linuxfoundation.org>
 <20180511193801.GA1940@dcvr>
 <bfb821ca-6082-8559-9476-b879a18a66ba@linuxfoundation.org>
 <20180516051206.GA16155@dcvr>
 <CAMwyc-RyEzoAXY0U6C0n_72MmYzMtCz2Z04AQaRZPjH2T1oXjw@mail.gmail.com>
 <20180524084115.GA17965@dcvr>
 <6f5ed36c-95db-86d8-291e-9dce0640b772@linuxfoundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <6f5ed36c-95db-86d8-291e-9dce0640b772@linuxfoundation.org>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On 05/24/18 04:41, Eric Wong wrote:
> > OK, that Xapian bug should be worked around in
> > https://public-inbox.org/meta/20180524083216.30440-1-e@80x24.org/
> > 
> > And pushed as commit c339a14b11c57e7b330f4efef6903bcbea2b3463
> > ("workaround Xapian OFD locks w/o close-on-exec")
> 
> Hmm... I'm still getting the same error, though, if I try to re-run
> public-inbox-index:
> 
> $ git clone --mirror https://public-inbox.org/meta

<snip>

> $ public-inbox-index /var/lib/public-inbox/meta.git
> 
> The above succeeds, but if I try to run it again right away:
> 
> $ public-inbox-index /var/lib/public-inbox/meta.git
> Exception: Unable to get write lock on
> /var/lib/public-inbox/meta.git/public-inbox/xapian15: already locked

Odd, I tried that exact sequence with the v1.2.22 tag in
xapian.git on my Debian machine to reproduce the problem
and make that patch.

> Is this easier solved by upgrading to the version of xapian > 1.2.22? I
> can probably nag the Epel packager to do that if it's a legitimate bug
> in Xapian.

Maybe... I wonder if there's other patches in the Epel package
or other system-level differences causing this.