user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Olly Betts <olly@survex.com>
Cc: 808610@bugs.debian.org, John Kozak <jk@thameslighter.net>,
	meta@public-inbox.org
Subject: Re: Bug#808610: libxapian22: xapian database corruption causes recollindex loop
Date: Thu, 3 Mar 2016 04:00:40 +0000	[thread overview]
Message-ID: <20160303040040.GA25654@dcvr.yhbt.net> (raw)
In-Reply-To: <20160303031645.GD18908@survex.com>

Olly Betts <olly@survex.com> wrote:
> On Thu, Mar 03, 2016 at 01:52:45AM +0000, Eric Wong wrote:
> > 
> > I would greatly appreciate a backport to fix this in Jessie.
> 
> A backport would only fix it for people who take special action and
> install from backports (that said, it's probably time to do a backport
> so there's a more up to date upstream version easily available for
> those who want it).

Errm, sorry, I meant "backport" as a general term for getting
a patch into jessie for all jessie users.
I forgot the Debian meaning of it is slightly different.

> In https://trac.xapian.org/ticket/645 the recoll upstream
> maintainer indicated that this happens with 1.2.8 too, and
> wheezy has 1.2.12-2 currently, so this issue also affects
> wheezy.

Interesting.  I haven't used Xapian extensively, but have never
seen problems on wheezy using the same hardware that was able
to reproduce the bug on jessie.

      reply	other threads:[~2016-03-03  4:00 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
2016-03-03  1:52         ` Eric Wong
2016-03-03  3:16           ` Olly Betts
2016-03-03  4:00             ` Eric Wong [this message]

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: http://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=20160303040040.GA25654@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).