Changelog for mingw64-libxapian30-1.4.21-2.151.noarch.rpm :

* Tue Nov 08 2022 Ralf Habacker - Update to version 1.4.21
* Add patch xapian-core-1.4.21-std-fixes.patch to fix (boo#1205190)
* Mon Apr 29 2019 ralf.habackerAATTfreenet.de- port to mingw64
* Thu Dec 14 2017 alarrosaAATTsuse.com- Update to 1.4.5:
* Add Database::get_total_length() method. Previously you had to calculate this from get_avlength() and get_doccount(), taking into account rounding issues. But even then you couldn\'t reliably get the exact value when total length is large since a double\'s mantissa has more limited precision than an unsigned long long.
* Add Xapian::iterator_rewound() for bidirectional iterators, to test if the iterator is at the start (useful for testing whether we\'re done when iterating backwards).
* DatabaseOpeningError exceptions now provide errno via get_error_string() rather than turning it into a string and including it in the exception message.
* WritableDatabase::replace_document(): when passed a Document object which came from a database and has unmodified values, we used to always read those values into a memory structure. Now we only do this if the document is being replaced to the same document ID which it came from, which should make other cases a bit more efficient.
* Enquire::get_eset(): When approximating term frequencies we now round to the nearest integer - previously we always rounded down.
* See also https://xapian.org/docs/xapian-core-1.4.5/NEWS
* Fri Jun 30 2017 alarrosaAATTsuse.com- Update to 1.4.4:
* Database::check(): + Fix checking a single table - changes in 1.4.2 broke such checks unless you specified the table without any extension. + Errors from failing to find the file specified are now thrown as DatabaseOpeningError (was DatabaseError, of which DatabaseOpeningError is a subclass so existing code should continue to work). Also improved the error message when the file doesn\'t exist is better.
* Drop OP_SCALE_WEIGHT over OP_VALUE_RANGE, OP_VALUE_GE and OP_VALUE_LE in the Query constructor. These operators always return weight 0 so OP_SCALE_WEIGHT over them has no effect. Eliminating it at query construction time is cheap (we only need to check the type of the subquery), eliminates the confusing \"0
* \" from the query description, and means the OP_SCALE_WEIGHT Query object can be released sooner. Inspired by Shivanshu Chauhan asking about the query description on IRC.
* Drop OP_SCALE_WEIGHT on the right side of OP_AND_NOT in the Query constructor. OP_AND_NOT takes no weight from the right so OP_SCALE_WEIGHT has no effect there. Eliminating it at query construction time is cheap (just need to check the subquery\'s type), eliminates the confusing \"0
* \" from the query description, and means the OP_SCALE_WEIGHT object can be released sooner.
* See also https://xapian.org/docs/xapian-core-1.4.4/NEWS
* Wed Feb 01 2017 alarrosaAATTsuse.com- Update to 1.4.3:
* MSet::snippet(): Favour candidate snippets which contain more of a diversity of matching terms by discounting the relevance of repeated terms using an exponential decay. A snippet which contains more terms from the query is likely to be better than one which contains the same term or terms multiple times, but a repeated term is still interesting, just less with each additional appearance. Diversity issue highlighted by Robert Stepanek\'s patch in https://github.com/xapian/xapian/pull/117 - testcases taken from his patch.
* MSet::snippet(): New flag SNIPPET_EMPTY_WITHOUT_MATCH to get an empty snippet if there are no matches in the text passed in. Implemented by Robert Stepanek.
* Round MSet::get_matches_estimated() to an appropriate number of significant figures. The algorithm used looks at the lower and upper bound and where the estimate sits between them, and then picks an appropriate number of significant figures. Thanks to Sébastien Le Callonnec for help sorting out a portability issue on OS X.
* Add Database::locked() method - where possible this non-invasively checks if the database is currently open for writing, which can be useful for dashboards and other status reporting tools.
* See also https://xapian.org/docs/xapian-core-1.4.3/NEWS- Update to 1.4.2:
* Add XAPIAN_AT_LEAST(A,B,C) macro.
* MSet::snippet(): Optimise snippet generation - it\'s now ~46% faster in a simple test.
* Add Xapian::DOC_ASSUME_VALID flag which tells Database::get_document() that it doesn\'t need to check that the passed docid is valid. Fixes #739, reported by Germán M. Bravo.
* TfIdfWeight: Add support for the L wdf normalisation. Patch from Vivek Pal.
* BB2Weight: Fix weights when database has just one document. Our existing attempt to clamp N to be at least 2 was ineffective due to computing N - 2 < 0 in an unsigned type.
* DPHWeight: Fix reversed sign in quadratic formula, making the upper bound a tiny amount higher.
* DLHWeight: Correct upper bound which was a bit too low, due to flawed logic in its derivation. The new bound is slightly less tight (by a few percent).
* DLHWeight,DPHWeight: Avoid calculating log(0) when wdf is equal to the document length.
* TermGenerator: Handle stemmer returning empty string - the Arabic stemmer can currently do this (e.g. for a single tatweel) and user stemmers can too. Fixes #741, reported by Emmanuel Engelhart.
* Database::check(): Fix check that the first docid in each doclength chunk is more than the last docid in the previous chunk - this code was in the wrong place so didn\'t actually work.
* Database::get_unique_terms(): Clamp returned value to be <= document length. Ideally get_unique_terms() ought to only count terms with wdf > 0, but that\'s expensive to calculate on demand.
* See also https://xapian.org/docs/xapian-core-1.4.2/NEWS
* Fri Nov 11 2016 alarrosaAATTsuse.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 09 2016 tittiatcokeAATTgmail.com- Update to 1.4.0
* API + Update to Unicode 9.0.0 + Reimplement ESet and ESetIterator + MSetIterator and ESetIterator are now STL-compatible random_access_iterators
* See also http://xapian.org/docs/xapian-core-1.4.0/NEWS
* Wed Apr 13 2016 tittiatcokeAATTgmail.com- Update to 1.2.23
* API + PostingSource: Public member variables are now wrapped by methods
* chert backend + xapian-check now performs additional consistency checks for chert.
* omega + Fix HTML/XML entity decoding to be O(n) not O(n²) - indexing HTML/XML with a lot of entities is now much faster.
* Thu May 21 2015 tittiatcokeAATTgmail.com- Update to 1.2.21
* API: + QueryParser: Extend the set of characters allowed in the start of a range to be anything except for \'(\' and characters <= \' \'.
* matcher: + Reimplement OP_PHRASE for non-exact phrases. + Reimplement OP_NEAR - the new implementation consistently requires the terms to occur at different positions, and fixes some previously missed matches. + Fix a reversed check for picking the shorter position list for an exact phrase of two terms. + When matching an exact phrase, if a term doesn\'t occur where we want, use its actual position to advance the anchor term, rather than just checking the next position of the anchor term.
* brass backend: + Fix cursor versioning to consider cancel() and reopen() as events where the cursor version may need incrementing, and flag the current cursor version as used when a cursor is rebuilt. + Avoid using file descriptions < 3 for writable database tables, as it risks corruption if some code in the same process tries to write to stdout or stderr without realising it is closed.
* chert backend: + Fix cursor versioning to consider cancel() and reopen() as events where the cursor version may need incrementing, and flag the current cursor version as used when a cursor is rebuilt. + Avoid using file descriptions < 3 for writable database tables, as it risks corruption if some code in the same process tries to write to stdout or stderr without realising it is closed.
* flint backend: + Fix cursor versioning to consider cancel() and reopen() as events where the cursor version may need incrementing, and flag the current cursor version as used when a cursor is rebuilt.
* remote backend: + Fix sort by value when multiple databases are in use and one or more are remote.
* build system: + The compiler ABI check in the public API headers now issues a warning (instead of an error) for an ABI mismatch for ABI versions 2 and later (which means GCC >= 3.4). + xapian-config,xapian-core.pc: When compiling with xlC on AIX, the reported --cxxflags/--cflags now include -D_LARGE_FILES=1 as this is defined for the library, and defining it changes the ABI of std::string with this compiler, so it must also be defined when building code using the Xapian API. + xapian-core.pc: Include --enable-runtime-pseudo-reloc in --libs output for mingw and cygwin, like xapian-config does. + xapian-core.pc: Fix include directory reported by `pkg-config --cflags`. + xapian-config: Fix typo so cached result of test in is_uninstalled() is actually used on subsequent calls. + configure: Changes in 1.2.19 broke the custom macro we use to probe for supported compiler flags such that the flags never got used. + configure: Set default value for AUTOM4TE before AC_OUTPUT so the default will actually get used. + soaktest: Link with libtool\'s \'-no-install\' or \'-no-fast-install\', like we already do for other test programs, which means that libtool doesn\'t need to generate shell script wrappers for them on most platforms.
* documentation: + API documentation: Minor wording tweaks and formatting improvements. + docs/deprecation.rst: Add deprecation of omindex --preserve-nonduplicates which happened in 1.2.4. + HACKING: libtool 2.4.6 is now used for bootstrapping snapshots and releases.
* tools: + xapian-compact: Make sure we open all the tables of input databases at the same revision. + xapian-metadata: Add \'list\' subcommand to list all the metadata keys. + xapian-replicate: Fix connection timeout to be 10 seconds rather than 10000 seconds (the incorrect timeout has been the case since 1.2.3). + xapian-replicate: Set SO_KEEPALIVE for xapian-replicate\'s connection to the master, and add command line option to allow setting socket-level timeouts (SO_RCVTIMEO and SO_SNDTIMEO) on platforms that support them. + xapian-replicate-server: Avoid potentially reading uninitialised data if a changeset file is truncated.
* portability: + Add spaces between literal strings and macros which expand to literal strings for C++11 compatibility. + ValueCountMatchSpy::top_values_begin(): Fix the comparison function not to return true for two equal elements, which manifests as incorrect sorting in some cases when using clang\'s libc++ (which recent OS X versions do). + apitest: The adddoc5 testcase fails under clang due to an exception handling bug, so just #ifdef out the problematic part of the testcase when building with clang for now. + configure: Improve the probe for whether the test harness can use RTTI to work for IBM\'s xlC compiler (which defaults to not generating RTTI). + Use F_DUPFD where available to dup to a file descriptor which is >= 2, rather than calling dup() until we get one. + When unserialising a double, avoid reading one byte past the end of the serialised value. + When unserialising a double, add missing cast to unsigned char when we check if the value will fit in the double type. + Fix incorrect use of \"delete\" which should be \"delete []\". This is undefined behaviour in C++, though the type is POD, so in practice this probably worked OK on many platforms.- Drop patch 0001-backends-chert-chert_cursor.cc-backends-chert-chert_.patch due to upstream inclusion
* Sat May 02 2015 hrvoje.senjanAATTgmail.com- Add 0001-backends-chert-chert_cursor.cc-backends-chert-chert_.patch from upstream (kde#341990, http://trac.xapian.org/ticket/675)