Control: tag -1 moreinfo On Mon, Dec 28, 2015 at 02:45:43AM +0000, Olly Betts wrote: > On Mon, Dec 21, 2015 at 01:14:40PM +0000, John Kozak wrote: > > I run recollindex from a crontab every night against a corpus of pdf > > files. After upgrading to jessie, every few days this update would go > > into a cpu busy loop, requiring the process to be killed and the > > database to be deleted and remade. Rebuilding `xapian-core` using the > > 1.2.21_git68 version of xapian-core from the xapian project has fixed this.
That means whatever the fix is, it's in 1.2.22, so packaging the latest upstream version will address this for unstable and testing. > To get this fixed in jessie, the SRMs aren't going to allow an update to > a new upstream version - they'll want a minimal patch. So we're going > to need to work out which change fixed this. > > 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). > > You mention database corruption in the subject line - does the database > also get reported as corrupt if you run xapian-check on it? Still awaiting your response on this. Cheers, Olly
