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: Mon, 29 Feb 2016 04:15:05 +0000 [thread overview]
Message-ID: <20160229041505.GA9299@dcvr.yhbt.net> (raw)
In-Reply-To: <20160120014515.GA21372@gemse>
Olly Betts <olly@survex.com> 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
> >
> > Can you test 1.2.19 plus that patch to see if this solves your problem?
> >
> > (If that is the fix, then testing and unstable aren't affected).
>
> Still awaiting your response on this.
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...
Meanwhile, in case anybody isn't familiar with patching + building
Debian packages.... (and most of my Debian knowledge is 15 years old,
so maybe I'm not up-to-date with latest practices).
Download the unified diff from the above Trac URL, it should
save to a file like:
changeset_826d1a19cc356e7bf66c1681626e70af32967447.diff
Make sure deb-src lines for jessie are available in
/etc/apt/sources.list (or a file in /etc/apt/sources.list.d/)
deb-src http://http.us.debian.org/debian/ jessie-updates main
deb-src http://http.us.debian.org/debian/ jessie main
deb-src http://http.us.debian.org/debian/ jessie-backports main
# install build prereqs (need root):
sudo apt-get update # make sure deb-src sources are known
sudo apt-get install build-essential fakeroot
sudo apt-get build-dep xapian-core
# grab the source (as a normal user)
apt-get source xapian-core=1.2.19-1
# enter the unpatched source directory
cd xapian-core-1.2.19
# apply the patch you downloaded above
# you'll see some warnings about fuzz which seem harmless for this:
patch -p1 </path/to/changeset_826d1a19cc356e7bf66c1681626e70af32967447.diff
# Still in the xapian-core-1.2.19 dir, run the build and wait a while:
debian/rules build
# build the Debian binary packages (.deb files)
fakeroot debian/rules binary
# At the end, you should see messages about .deb files being
# built in the parent directory, install the libxapian22 deb:
sudo dpkg -i ../libxapian22_1.2.19-1_amd64.deb
I'm testing this against t/search.t in the public-inbox.git sources
# fetch prereqs and sources:
sudo apt-get install libsearch-xapian-perl libemail-mime-perl
git clone git://80x24.org/public-inbox
# enter the source tree
cd public-inbox
# reset to the HEAD as of this writing
git reset --hard 9bae4c858d983d0f0cf7314b50f613818a58d5c5
# Audit t/search.t and any files it uses/requires (in lib)
# to ensure it won't eat your hard drive or send me all your
# personal info :)
# test in a loop:
while perl -I lib t/search.t; do :; done
# let the loop run for a few hours/days...
Even without the patch, it can take thousands of tries before a
failure manifests along the lines of:
Exception: find_entry failed to find any entry at all!
Or something with "basic_string" in it...
I never had any problems under Debian wheezy.
next parent reply other threads:[~2016-02-29 4:15 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 ` Eric Wong [this message]
2016-03-01 8:41 ` Bug#808610: libxapian22: xapian database corruption causes recollindex loop Eric Wong
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: 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=20160229041505.GA9299@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).