Hello community, here is the log from the commit of package xapian-core for openSUSE:Factory checked in at 2016-11-14 20:10:24 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/xapian-core (Old) and /work/SRC/openSUSE:Factory/.xapian-core.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "xapian-core" Changes: -------- --- /work/SRC/openSUSE:Factory/xapian-core/xapian-core.changes 2016-08-18 10:17:59.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.xapian-core.new/xapian-core.changes 2016-11-14 20:10:26.000000000 +0100 @@ -1,0 +2,81 @@ +Fri Nov 11 10:02:34 UTC 2016 - alarr...@suse.com + +- Update to 1.4.1 + * Constructing a Query for a non-reference counted PostingSource object will + now try to clone the PostingSource object (as happened in 1.3.4 and + earlier). This clone code was removed as part of the changes in 1.3.5 to + support optional reference counting of PostingSource objects, but that breaks + the case when the PostingSource object is on the stack and goes out of scope + before the Query object is used. Issue reported by Till Schäfer and analysed + by Daniel Vrátil in a bug report against Akonadi: + https://bugs.kde.org/show_bug.cgi?id=363741 + + * Add BM25PlusWeight class implementing the BM25+ weighting scheme, implemented + by Vivek Pal (https://github.com/xapian/xapian/pull/104). + + * Add PL2PlusWeight class implementing the PL2+ weighting scheme, implemented + by Vivek Pal (https://github.com/xapian/xapian/pull/108). + + * LMWeight: Implement Dir+ weighting scheme as DIRICHLET_PLUS_SMOOTHING. + Patch from Vivek Pal. + + * Add CoordWeight class implementing coordinate matching. This can be useful + for specialised uses - e.g. to implement sorting by the number of matching + filters. + + * DLHWeight,DPHWeight,PL2Weight: With these weighting schemes, the formulae + can give a negative weight contribution for a term in extreme cases. We + used to try to handle this by calculating a per-term lower bound on the + contribution and subtracting this from the contribution, but this idea + is fundamentally flawed as the total offset it adds to a document depends on + what combination of terms that document matches, meaning in general the + offset isn't the same for every matching document. So instead we now clamp + each term's weight contribution to be >= 0. + + * TfIdfWeight: Always scale term weight by wqf - this seems the logical + approach as it matches the weighting we'd get if we weighted every non-unique + term in the query, as well as being explicit in the Piv+ formula. + + * Fix OP_SCALE_WEIGHT to work with all weighting schemes - previously it was + ignored when using PL2Weight and LMWeight. + + * PL2Weight: Greatly improve upper bound on weight: + + Split the weight equation into two parts and maximise each separately as + that gives an easily solvable problem, and in common cases the maximum is + at the same value of wdfn for both parts. In a simple test, the upper + bounds are now just over double the highest weight actually achieved - + previously they were several hundred times. This approach was suggested by + Aarsh Shah in: https://github.com/xapian/xapian/pull/48 + + Improve upper bound on normalised wdf (wdfn) - when wdf_upper_bound > + doclength_lower_bound, we get a tighter bound by evaluating at + wdf=wdf_upper_bound. In a simple test, this reduces the upper bound on + wdfn by 36-64%, and the upper bound on the weight by 9-33%. + + * PL2Weight: Fix calculation of upper_bound when P2>0. P2 is typically + negative, but for a very common term it can be positive and then we should + use wdfn_lower not wdfn_upper to adjust P_max. + + * Weight::unserialise(): Check serialised form is empty when unserialising + parameter-free schemes BoolWeight, DLHWeight and DPHWeight. + + * TermGenerator::set_stopper_strategy(): New method to control how the Stopper + object is used. Patch from Arnav Jain. + + * QueryParser: Fix handling of CJK query over multiple prefixes. Previously + all the n-gram terms were AND-ed together - now we AND together for each + prefix, then OR the results. Fixes #719, reported by Aaron Li. + + * Add Database::get_revision() method which provides access to the database + revision number for chert and glass, intended for use by xapiand. Marked + as experimental, so we don't have to go through the usual deprecation cycle + if this proves not to be the approach we want to take. Fixes #709, + reported by German M. Bravo. + + * Mark RangeProcessor constructor as `explicit`. + + * See also https://xapian.org/docs/xapian-core-1.4.1/NEWS + +- A compiler with support for C++11 is required, so + specify BuildRequires gcc-c++ >= 4.6 + +------------------------------------------------------------------- Old: ---- xapian-core-1.4.0.tar.xz xapian-core-1.4.0.tar.xz.asc New: ---- xapian-core-1.4.1.tar.xz xapian-core-1.4.1.tar.xz.asc ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ xapian-core.spec ++++++ --- /var/tmp/diff_new_pack.8qTwZJ/_old 2016-11-14 20:10:27.000000000 +0100 +++ /var/tmp/diff_new_pack.8qTwZJ/_new 2016-11-14 20:10:27.000000000 +0100 @@ -17,7 +17,7 @@ Name: xapian-core -Version: 1.4.0 +Version: 1.4.1 Release: 0 Summary: The Xapian Probabilistic Information Retrieval Library License: GPL-2.0 @@ -29,7 +29,7 @@ Source3: baselibs.conf BuildRequires: automake BuildRequires: fdupes -BuildRequires: gcc-c++ +BuildRequires: gcc-c++ >= 4.6 BuildRequires: libuuid-devel BuildRequires: pkg-config BuildRequires: xz ++++++ xapian-core-1.4.0.tar.xz -> xapian-core-1.4.1.tar.xz ++++++ ++++ 71398 lines of diff (skipped)
