similar to: Xapian 1.3.7 development snapshot released

I'm happy to be able to announce that Xapian 1.3.6 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. We're pretty close to a stable 1.4.0 release at this point - there's currently only one ticket still pegged on 1.3.x, which is to sort out some details of the

Xapian 1.3.0 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 so that 1.4.0 can both happen sooner and be better than otherwise. 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

After rather longer than expected, Xapian 1.3.1 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 so that 1.4.0 can both happen sooner and be better than otherwise. 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

I'm happy to be able to announce that Xapian 1.3.5 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. We're closing in on a stable 1.4 release series, so please consider trying this out with your code if you haven't already. There's not a set release date for 1.4.0,

On Fri, 01 Jan 2016 at 18:19, Olly Betts wrote: >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

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

I'm happy to be able to announce that Xapian 1.3.3 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

hi i?m trying to build the ruby bindings in xapian 1.1.2 on win xp. i?ve 1. pulled the tags/1.1.2 revision from svn 2. built SWIG from repo via MinGW and MSYS (swig -help works, so build seems ok to me) 3. built xapian-core following readme in ...\win32msvc, apitest doesn?t give errors now if i try to build: "...\ruby>nmake SWIGBUILD=1 Microsoft (R) Program

I've released Xapian 1.1.4. We're getting really close to releasing a stable 1.2.0, and I think this is a possible release candidate. So please try it out and report any issues you find. We're hopefully looking at a 1.2.0 release later this month. However, this is still nominally a development release with the usual provisos about ABI and database formats potentially being subject

Hi folks, I spotted an HTML escaping bug in Xapian::MSet::snippet() while working on the code. This issue has been assigned CVE-2018-0499 (though currently there's no useful information on cve.mitre.org for it). I've added a wiki page for it here: https://trac.xapian.org/wiki/SecurityFixes/2018-07-02 The intended behaviour is that the selected input text is escaped for use in HTML,

This is an updated release announcement for Xapian 1.1.4. The change is that the previous version had a xapian-core tarball which hadn't had its version bumped from 1.1.3 (but all other changes intended to be in it were present). I've updated the version and rebuilt that tarball. The others are unchanged. I'll preserve the rest of the announcement below (aside from updating the

Hi, Olly: I post the error in the attachment, any methods to fix it? Run the command (.\lemon.exe -q -oqueryparser_internal.cc -hqueryparser_token.h queryparser.lemony) will get the error. If it is hard to fix, I will upgrade xapian to 1.4. But I worry it will cost me too much time to modify my application code. Thanks a lot. Here is the error details: lemon.c: #define LISTSIZE 30

I've released Xapian 1.1.5. We're getting really close to releasing a stable 1.2.0, and this is a possible release candidate. So please try it out and report any issues you find. We're hopefully looking at a 1.2.0 release later this month. However, this is still nominally a development release with the usual provisos about ABI and database formats potentially being subject to

hi, Olly Betts, Thank you for you answer. My xapian version is 1.2.8. Need I upgrade it to 1.4 if I want to build it with MSVC2017 x64? lishu at fiberhome.com From: Olly Betts Date: 2018-03-29 11:10 To: 李澍; xapian-discuss Subject: Re: how to build 64bit xapian using MSVC2017? On Tue, Mar 20, 2018 at 08:28:24PM +0000, Olly Betts wrote: > Related to this, the appveyor build is

On Mon, Mar 19, 2018 at 03:31:38PM +0800, 李澍 wrote: > I'm new in xapian project. I want to build 64bit xapian(1.2.8) from > source using MSVC 2017. The 1.2.x release series was retired about 6 months ago, and 1.2.8 is far from being the latest version even in that retired release series (it's more than 6 years old). For a stable release, please use 1.4.x. In particular, there are

I'm cc:-ing my reply to xapian-devel, since others may have an opinion. In particular, James has probably done most work on the python bindings. On Fri, Jan 27, 2006 at 03:56:23PM -0800, Jason Toffaletti wrote: > I'm curious if boost::python has been considered for creating more > pythonic bindings to Xapian. I've used it to wrap several C++ libraries > and found the

On Tue, Mar 20, 2018 at 08:28:24PM +0000, Olly Betts wrote: > Related to this, the appveyor build is currently failing on git master. > Unfortunately the change at which is started to fail was the addition > of the new "honey" backend, which doesn't narrow things down to a > useful degree. I've disabled honey in these builds for now. This really needs to be

Hello, Thank you very much for quick response. I need only xapian-core. As I wrote on my case compilation with Visual Studio 2015 successful, just I have runtime errors, while the same code on LINUX runs fine. I'll try the hints from (https://trac.xapian.org/browser/git/xapian-core/INSTALL?rev=RELEASE/1.4#L54) and maybe to migrate my project to VS2017 and test it again. If I understand

Thank's !! I'll try during the week, and will let you know if all is fine ;) Le mar. 10 juil. 2018 à 07:36, Olly Betts <olly at survex.com> a écrit : > On Mon, Jul 09, 2018 at 10:29:18AM +0100, Olly Betts wrote: > > The attached patch reset this cursor each time commit() is called, and > > that fixes my C++ reproducer, though I think this ought to work as-is >

On Mon, Jul 09, 2018 at 10:29:18AM +0100, Olly Betts wrote: > The attached patch reset this cursor each time commit() is called, and > that fixes my C++ reproducer, though I think this ought to work as-is > and the real bug is at a lower level. I've dug deeper and that was indeed the case. Here's a patch which addresses the root cause: