From: Eric Wong <e@80x24.org>
To: 808610@bugs.debian.org
Cc: John Kozak <jk@thameslighter.net>, Olly Betts <olly@survex.com>,
meta@public-inbox.org
Subject: Re: Bug#808610: libxapian22: xapian database corruption causes recollindex loop
Date: Tue, 1 Mar 2016 08:41:37 +0000 [thread overview]
Message-ID: <20160301084137.GA29377@dcvr.yhbt.net> (raw)
In-Reply-To: <20160229041505.GA9299@dcvr.yhbt.net>
Eric Wong <e@80x24.org> wrote:
> > On Mon, Dec 28, 2015 at 02:45:43AM +0000, Olly Betts wrote:
> > > There haven't been many backend changes since 1.2.19 - my guess is it's
> > > this one:
> > >
> > > http://trac.xapian.org/changeset/826d1a19cc356e7bf66c1681626e70af32967447/git
>
> I encountered a problem with Jessie, too, and this might be it.
> I'm testing the above change on the public-inbox.git tree
> (instructions below). Will update in 24-48 hours...
28 hours or so and my loop (below) is still going! \o/
I think the longest it ran previously was maybe an hour or two.
I'll let it run another day to be certain, but I'm fairly
certain this needs to be backported for Jessie users.
<snip>
> while perl -I lib t/search.t; do :; done
next prev parent reply other threads:[~2016-03-01 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ygepoy054fz.fsf@renn.unassigned-domain>
[not found] ` <20151228024543.GC25782@survex.com>
[not found] ` <20160120014515.GA21372@gemse>
2016-02-29 4:15 ` Bug#808610: libxapian22: xapian database corruption causes recollindex loop Eric Wong
2016-03-01 8:41 ` Eric Wong [this message]
2016-03-03 1:52 ` Eric Wong
2016-03-03 3:16 ` Olly Betts
2016-03-03 4:00 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160301084137.GA29377@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=808610@bugs.debian.org \
--cc=jk@thameslighter.net \
--cc=meta@public-inbox.org \
--cc=olly@survex.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).