Konstantin Ryabitsev <[email protected]> wrote: > On 05/24/18 04:41, Eric Wong wrote: > > OK, that Xapian bug should be worked around in > > https://public-inbox.org/meta/[email protected]/ > > > > 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. -- unsubscribe: [email protected] archive: https://public-inbox.org/meta/
