similar to: HEAD is broken

I've now got working (but not necessarily policy compliant) debian packages for xapian-core, the xapian python bindings, and omega and omindex. I will be sorting out a public apt repository of these shortly. Is it appropriate to add the debian control files (ie, those files in the debian directories in CVS) to the distribution tarballs? I think yes - they don't take up much space,

Hi, I'm confused about my licensing obligation with respect to the Xapian SWIG bindings. I've got a python wrapper that sits above the standard Xapian Python/SWIG bindings, and I wasn't sure if the *intent* of the Xapian team is that my python wrapper - and any code that also uses my wrapper also falls under GPLv2. It seems unclear if the FSF's position on dynamic linking in

Report by Eric Lindblad 11-09-2015 http://www.ericlindblad.blogspot.com I compiled xapian-core-1.0.23 today on Interix. 'gmake check' summary PASS: btreetest, quartztest, stemtest, termgentest FAIL: apitest, internaltest, queryparsertest MS XP SP3 HOME modified SFU Interix 3.5 w/ getopt.h, inttypes.h, & stdint.h copied over from SUA Interix for Vista (and newer) into

Report by Eric Lindblad 11-09-2015 http://www.ericlindblad.blogspot.com I compiled xapian-core-1.0.23 today on Interix. 'gmake check' summary PASS: btreetest, quartztest, stemtest, termgentest FAIL: apitest, internaltest, queryparsertest MS XP SP3 HOME modified SFU Interix 3.5 w/ getopt.h, inttypes.h, & stdint.h copied over from SUA Interix for Vista (and newer) into

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of

Xapian has turned 20! Strictly speaking it was 20 years ago last month but I managed to miss the true anniversary - the oldest commit in the Xapian repo is: commit 8ced76ea128c8fb2792477e09b41fa989f2e572f Author: Richard Boulton <richard at tartarus.org> Date: Fri Sep 10 09:50:40 1999 +0000 Martins initial code, which didn't work for him but did for me. Back then Richard,

Hi, As part of my whole indexing thing, I want to move the databases around, from within the code. So, I figured that the safest bet would be to close the DB before attempting to move it. But there's no Xapian::Database::close() or even Xapian::WritableDatabase::close(). I have a global variable that holds the database, and I open it in the main(): // globals Xapian::WritableDatabase

Yesterday I updated the deprecation.rst document such that I think it contains all the items which are slated for deprecation (and also contains full details of the upgrade suggestions, as Olly suggested). I've marked several things which have been deprecated for a long period of time (ie, since 0.9.0 or earlier) for removal in 1.0.0, in line with the policy outlined in the document. If

I'm new to Xapian and we just recently upgraded to version 1.0.0.0. However, something seems to have changed during the upgrade and I need help figuring out how my code should be written. In version 0.9.9.1 of Search::Xapian, the following code results in this output "Xapian::Query(pet:(pos=1))". my $qp = new Search::Xapian::QueryParser; $qp->set_stemmer(new

(Forwarded off-list message) -------- Original Message -------- Subject: Re: [Xapian-discuss] what is the fastest way to fetch results which are sorted by timestamp ? Date: Thu, 11 Aug 2011 01:06:36 +0800 From: ??? <panjunyong at gmail.com> To: Tim Brody <tdb2 at ecs.soton.ac.uk> On Wed, Aug 10, 2011 at 6:39 PM, Tim Brody <tdb2 at ecs.soton.ac.uk> wrote: > Hi, > > In

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8229 > Date: 2007-04-13 10:18:52 +0100 (Fri, 13 Apr 2007) > > Log message (4 lines): > api/version.cc: Simpler and cleaner fix - the prototypes for the > version functions had moved from xapian/version.h to xapian.h so we > were including the wrong header and not

I'm planning to add multiple-database support for searches to my "Xappy" python wrapper (more on this wrapper later, but for now, see http://code.google.com/p/xappy for details). This is reasonably straightforward, because Xapian supports this nicely: except that "Xappy" generates a "fieldname->prefix" mapping automatically. The prefix which corresponds

There's a bit of an API glitch with Query objects at present. This code shows it off: Xapian::Database("/path/to/db"); Xapian::Enquire enquire(db); // make a simple query Xapian::Query myquery(Xapian::Query::OP_NEAR, phrase, phrase + 2); enquire.set_query(myquery); // Now change the query - this shouldn't affect the query enquire // will run, but it does.

On Tuesday, I replaced the romanian1 and romanian2 stemmers in Xapian-core with Martin's new romanian stemmer. At the time, I also updated the stemming test data (by re-generating the output file using snowball's "stemwords" utility), and I clearly remember re-running the testsuite at the time and checking that all tests passed. Now, when I run make check, stemtest fails

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9092 > Date: 2007-06-30 15:16:16 +0100 (Sat, 30 Jun 2007) > > Log message (2 lines): > api/omdocument.cc,common/document.h,include/xapian/document.h: > Add Xapian::Document::get_docid() method. I was thinking that it would probably be useful to have a

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8351 > Date: 2007-04-23 01:44:44 +0100 (Mon, 23 Apr 2007) > > Log message (2 lines): > backends/flint/flint_version.cc: Update the flint format version > since older flint versions can't read compressed tags. Am I correct in assuming that this means that when

On Tue, May 11, 2004 at 05:41:58PM +0100, Richard Boulton wrote: > * If the queryserver can't parse a query, strip out all special > characters, and then retry. This means that we get some kind of > result even if the query is broken. That's probably a feature worth pushing down into Xapian::QueryParser... Cheers, Olly

On Thu, May 20, 2004 at 02:55:13PM +0100, Richard Boulton wrote: > Add debian packaging files to distribution tarball. > > Modified files: > xapian-core : Makefile.am You also need to add debian/Makefile.in to configure.in (I usually forget too). Probably debian/control.in too. Cheers, Olly

I'm happy to be able to announce that Xapian 1.3.4 is now available. Please note that 1.3.x releases are development releases - they are made to encourage earlier and wider use and testing of new and changed code. Our record with 1.1.x was very good - all the bugs I am aware of were either in new features, or were also present in the corresponding 1.0.x release. But if you main concern is

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 7759 > Date: 2007-02-26 18:38:13 +0000 (Mon, 26 Feb 2007) > > Log message (3 lines): > tests/harness/backendmanager.cc: Indent with tabs not spaces. Hmm - this space thing is getting silly - I have my editor set to not expand tabs, but spaces crept in because I