From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS8282 80.252.112.0/20 X-Spam-Status: No, score=-2.9 required=3.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_MED,SPF_PASS,URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: meta@public-inbox.org Received: from atreus.tartarus.org (atreus.tartarus.org [80.252.125.10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 9F4721F4E2; Thu, 3 Mar 2016 03:16:48 +0000 (UTC) Received: from olly by atreus.tartarus.org with local (Exim 4.69) (envelope-from ) id 1abJkr-0003HT-Te; Thu, 03 Mar 2016 03:16:45 +0000 Date: Thu, 3 Mar 2016 03:16:45 +0000 From: Olly Betts To: Eric Wong Cc: 808610@bugs.debian.org, John Kozak , meta@public-inbox.org Subject: Re: Bug#808610: libxapian22: xapian database corruption causes recollindex loop Message-ID: <20160303031645.GD18908@survex.com> References: <20151228024543.GC25782@survex.com> <20160120014515.GA21372@gemse> <20160229041505.GA9299@dcvr.yhbt.net> <20160301084137.GA29377@dcvr.yhbt.net> <20160303015245.GA6135@dcvr.yhbt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160303015245.GA6135@dcvr.yhbt.net> User-Agent: Mutt/1.5.21 (2010-09-15) List-Id: Control: tags -1 -moreinfo Control: tags -1 +wheezy Control: severity -1 grave On Thu, Mar 03, 2016 at 01:52:45AM +0000, Eric Wong wrote: > > > > On Mon, Dec 28, 2015 at 02:45:43AM +0000, Olly Betts wrote: > > > > > http://trac.xapian.org/changeset/826d1a19cc356e7bf66c1681626e70af32967447/git > > It's been longer than 24 hours, but yes, everything is still > good with the above change. > > 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). This database corruption means data loss, so I think this deserves a stable update with just the patch above. It doesn't touch many places, comes with a regression testcase, and has been in use without reported issues for 10 months. 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. > Stopping the test now since I've burned enough cycles for > now :) Thanks for the testing. Cheers, Olly