I've uploaded Xapian 1.0.13 (including Search::Xapian 1.0.13.0), which
as usual you can download from:
http://xapian.org/download
Here are the SHA1 checksums of the released files:
d90e7ea2ba000bf28947e5da820455594461637c Search-Xapian-1.0.13.0.tar.gz
2d8bd20b5dd1fc0554a1ac4be047e9b35310e000 xapian-bindings-1.0.13.tar.gz
c08eca16b8816e244cd30c35d2fe53d49f78cd77 xapian-core-1.0.13.tar.gz
9fcb1dd92c7d08e9ce3bbeba22086674dee272df xapian-omega-1.0.13.tar.gz
And for those worried about SHA1's strength, here are SHA256 checksums:
f6d2d86df70e97e0339974b6d7aaf0f2490550982fc903ce21e7ca68fa365021
Search-Xapian-1.0.13.0.tar.gz
bd57ab5db7dc4e33cbc8c25255823ec27f5a8812a62210f5711253db8e537300
xapian-bindings-1.0.13.tar.gz
a474be06657bd83200231d938d48d4d2a83cff0252c618421f835604c5548dce
xapian-core-1.0.13.tar.gz
f4300215b8ea57accee670ccc8ae2f840319966d21c8b725f2998d5ad4619728
xapian-omega-1.0.13.tar.gz
I have signed this announcement with my GPG key, so if you can establish a
trust chain to my key, and you verify the checksums, you can be confident that
the tarballs you downloaded are the same as those I uploaded (even if you get
them from a mirror). If you can't establish a trust chain, you can still
verify the checksums (and also see that the same key is being used to sign
each release announcement).
I'm intending to generate a new key in the near future, which I'll sign
with my current key and try to get a few other signatures on. I'll then
sign release announcements with both keys for a while.
This release fixes a few bugs, adds a couple of new little features, and
makes several performance improvements to the matcher.
Notable changes in this release:
* A long standing problem with deadlocks when trying to use the Python bindings
with mod_python has been worked around (the problem is due to bugs in
mod_python which are apparently unlikely to ever be fixed).
* scriptindex has a new "valuenumeric" action for indexing values
suitable for
numeric sorting.
* Perl has a new set of example programs.
* The Perl bindings have a new Search::Xapian::MSet::matches() method which
ties the MSet to a Perl array (like Search::Xapian::Enquire::matches(), but
this method makes more sense on MSet than Enquire. However, I've just
spotted I failed to apply a patch where I changed my mind and called this
"items()" (for consistency with a patch on trunk to add support for
tying
ESet objects to arrays - also Python has 'MSet.items' and
'ESet.items'
properties, and while consistency between the Perl and Python bindings is not
so important for most users, it's not a bad thing). So I guess consider
the
new method deprecated already - I'll see if I can find time to put
1.0.13.1
out soon.
For a more detailed overview see:
http://trac.xapian.org/wiki/ReleaseOverview/1.0.13
The full lists of user-visible changes are linked to from there, and
from the "[news]" links on the download page.
As always, if you encounter problems, please report them here, or to
the bug-tracker: http://xapian.org/bugs
A new development release (1.1.1) should be out later this week too.
Cheers,
Olly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url :
http://lists.xapian.org/pipermail/xapian-discuss/attachments/20090525/30d64777/attachment.pgp
On Mon, May 25, 2009 at 06:24:40PM +1200, Olly Betts wrote:> * The Perl bindings have a new Search::Xapian::MSet::matches() method which > ties the MSet to a Perl array (like Search::Xapian::Enquire::matches(), but > this method makes more sense on MSet than Enquire. However, I've just > spotted I failed to apply a patch where I changed my mind and called this > "items()" (for consistency with a patch on trunk to add support for tying > ESet objects to arrays - also Python has 'MSet.items' and 'ESet.items' > properties, and while consistency between the Perl and Python bindings is > not so important for most users, it's not a bad thing). So I guess > consider the new method deprecated already - I'll see if I can find time to > put 1.0.13.1 out soon.OK, done. Download from: http://xapian.org/download SHA1 checksum: 702972d57b895044de92e7f827af9d31151c66db Search-Xapian-1.0.13.1.tar.gz SHA256 checksum: e3ba9f9ebe0018c93a300579c7d7dab2f14890001e0e7d172cf3464f48bcef01 Search-Xapian-1.0.13.1.tar.gz Changes over 1.0.13.0 are: - Deprecate Search::Xapian::MSet::matches() and make it issue a warning. Please use Search::Xapian::MSet::items() instead. - Add another translated example: simplematchdecider.pl Cheers, Olly -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.xapian.org/pipermail/xapian-discuss/attachments/20090527/acc402e6/attachment.pgp
Hi Olly, Just to clarify (I'm not sure whether I'm Arthur or Martha today, and my vein is starting to throb): To successfully use the latest svn/xapian-core (to play with CHERT), which Perl Search-Xapian should I use? CPAN, svn:xapian/search-xapian or http://oligarchy.co.uk/xapian/1.0.13/Search-Xapian-1.0.13.1.tar.gz? CPAN (as you mention on the site) seems out of date, and I'm having compile problems (which I'll detail here once I know what to compile with). Thanks Henry
Olly Betts wrote:> I've uploaded Xapian 1.0.13 (including Search::Xapian 1.0.13.0)Are you planning on updating the PPA for Xapian backports soon? https://launchpad.net/~xapian-backports/+archive/ppa We'd like to update, but are currently using Dapper. Thanks! Jim
Olly Betts wrote:> I've uploaded Xapian 1.0.13 (including Search::Xapian 1.0.13.0), which > as usual you can download from: > > http://xapian.org/downloadHi all, Build files and prebuilt binaries for Windows are now available at http://www.flax.co.uk/xapian_windows.shtml Sorry for the delay, Cheers Charlie
Olly Betts
2009-Jun-07 12:33 UTC
[Xapian-discuss] Installing svn (was Xapian 1.0.13 released)
On Wed, Jun 03, 2009 at 09:47:48AM +0200, Henry wrote:> It looks like I was having a spot of bother getting the svn to run > correctly because make was using /usr/local/bin/xapian-config instead > of /usr/local/bin/xapian-config-1.1 (ie, at some point I had also > installed the stable version).Aha, this is actually a bug in bootstrap in SVN trunk - it uses "xapian-config" instead of "xapian-config-1.1". Fixed in r12853. Cheers, Olly