diff --git a/xapian-core-1.4.0.tar.xz b/xapian-core-1.4.0.tar.xz deleted file mode 100644 index 84e2d8d..0000000 --- a/xapian-core-1.4.0.tar.xz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:10584f57112aa5e9c0e8a89e251aecbf7c582097638bfee79c1fe39a8b6a6477 -size 2613272 diff --git a/xapian-core-1.4.0.tar.xz.asc b/xapian-core-1.4.0.tar.xz.asc deleted file mode 100644 index 1c2930a..0000000 --- a/xapian-core-1.4.0.tar.xz.asc +++ /dev/null @@ -1,17 +0,0 @@ ------BEGIN PGP SIGNATURE----- -Version: GnuPG v1 - -iQIcBAABCAAGBQJXbsiLAAoJEBgUewc7rSsHBTwQANt8rAb66Jr8CutrOjSnyin/ -t//9mtq3mDOkB4YuhOMU6IMtZcS21lSiq4ZD8FLBHJQLKpvRutau7NGzRcseSlHP -GQe6NpJ6Zuy3zbuYt3lI7W17mS9J9TwahdQNsHOniUAlcP+CPobAP9Gahdmc0GaR -oMMDR3Fni9hU65G0q3+N7dGJXcTUE6/h+StrDbFzjsG0rJZtJR+BTwYUThEhRonS -7Qpph5bEWx+d6/zlom8+qQHv/qxiCB2GDdiwoGiQ20RGw7tGATXsJPawuBM8H8b1 -k5bpDEvsOCmqOfwbvcCTwmcs2xdhDCB7jMHOuiXuuiH4eESKES6fyihbwiLUX3Vy -6b78/O05DSvk/hTNTdMxy0bgdIrCJvrqOmPWoGpnpHAGKJ0VyKmc6AxH3UwN2L7L -9po2EsunZ7XTrixeommga69zmgAD8FQfGYFu4xt8J69C2x1h+ZF/jY5Ws1PE5Afu -gSGvRZl8oI8Uh8D0V0cGjbYmLM9AkeZsB0dUfOJb5RNE4KBJU+QjZSquc68yhp6z -IpVYBOZhgYp+vjV7L5jd3OJhspx8fmCkCofMLyzpaj+HYlAtJ4qmDCJV5Sz1oZlu -BXr2oqRTAP04xizMS+7YRbYPkjk3QV1Bwu87NV143gGuJuP5PjRRhKjQ25qGsJFP -2t3TvK+JrSEbybGTswjd -=x/ke ------END PGP SIGNATURE----- diff --git a/xapian-core-1.4.1.tar.xz b/xapian-core-1.4.1.tar.xz new file mode 100644 index 0000000..f658820 --- /dev/null +++ b/xapian-core-1.4.1.tar.xz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5f2534de73c067ac19eed6d6bec65b7b2c1be00131c8867da9e1dfa8bce70eb +size 2793644 diff --git a/xapian-core-1.4.1.tar.xz.asc b/xapian-core-1.4.1.tar.xz.asc new file mode 100644 index 0000000..922e1fa --- /dev/null +++ b/xapian-core-1.4.1.tar.xz.asc @@ -0,0 +1,16 @@ +-----BEGIN PGP SIGNATURE----- + +iQIcBAABCAAGBQJYCbILAAoJEBgUewc7rSsHLQUQALq9t+U+yarnIH4Nd/sjbfus +3ek1tgxXsIMcp9AXTUhBJTEu/GkIXg+ABGnPIGq+kT2XnNcLZpVcchxrsTTtYGgh +M0Dq9ol2QBhgNsex26udKmD+diiUCY/ueUwiuBsKDHZClYR5sdmLwIhgki47ouQB +JU4NYF97Apo/rSkOSD93xtodOd8vjsREaDIPp+kPzvxE+uW2CSbOTFTEcPD6/BM5 +DpkQ18BZvcxtSwOMY7NfSrvTYHhj7pqf0c7IZnXEBSDncFVxCbmQHYbBGJrw5oa1 +etN3Nzg0hM/w2pLYFhnLPkrwj9Oxk0e0me9YnbUlCuQharnqT9Bn32pg3N6K95OZ +Y0oKRwxN3aDwPD7j4T6h/bu0yR4x8kg5j8a9aTq2sBDous56wmL7TiFgz4Qww6l9 +4Ik/BUNqNBKbGR5GDQLM/O2gzRKO/W5jnXq31lMkmftPqFT4t+mVuXutp8RWYlA+ +0TwE0EVTkIr+5xJWKRNmRoJgxbsLq1XET9oSNwhLfnGggkSXaklp3RNM7UmptYTW +3EpOQuGeyCZrQ1SXHaVw8oSqBzdflhpVwbA8QOvQxuaBh02z5z6l7HwMVNpVNM9G +cOWoJPpJ/qjcYK/wWqbefbPNJJn75LBkVFBp1Qj8oXGhzh11/nEKmhkwJOpSNLec +JETe8DkBjuGZlnlALv/n +=vAo5 +-----END PGP SIGNATURE----- diff --git a/xapian-core.changes b/xapian-core.changes index 3b319dc..786b63d 100644 --- a/xapian-core.changes +++ b/xapian-core.changes @@ -1,3 +1,84 @@ +------------------------------------------------------------------- +Fri Nov 11 10:02:34 UTC 2016 - alarrosa@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 + ------------------------------------------------------------------- Sat Jul 9 06:25:35 UTC 2016 - tittiatcoke@gmail.com diff --git a/xapian-core.spec b/xapian-core.spec index caedd6d..45aba01 100644 --- a/xapian-core.spec +++ b/xapian-core.spec @@ -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 @@ Source2: %{name}.keyring Source3: baselibs.conf BuildRequires: automake BuildRequires: fdupes -BuildRequires: gcc-c++ +BuildRequires: gcc-c++ >= 4.6 BuildRequires: libuuid-devel BuildRequires: pkg-config BuildRequires: xz