| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: libxapian-devel | Distribution: openSUSE Tumbleweed |
| Version: 1.4.32 | Vendor: openSUSE |
| Release: 1.1 | Build date: Fri Oct 2 07:44:28 2026 |
| Group: Development/Libraries/C and C++ | Build host: reproducible |
| Size: 530534 | Source RPM: xapian-core-1.4.32-1.1.src.rpm |
| Packager: http://bugs.opensuse.org | |
| Url: https://xapian.org/ | |
| Summary: Files needed for building packages which use Xapian | |
Xapian is a Probabilistic Information Retrieval library. It offers an adaptable toolkit for adding indexing and search facilities to applications. This subpackage contains the header files for the library.
GPL-2.0-only
* Fri Oct 02 2026 Matthias Fehring <buschmann23@opensuse.org>
- update to version 1.4.32
* API:
+ MSet::snippet(): Fix missing escaping when parameters hi_start
and hi_end are empty strings and text.size() <= length. This
is essentially a missed corner case from CVE-2018-0499.
* Portability:
+ configure: `-Wstrict-overflow=1` is no longer added to the
default compiler options for GCC and clang. This option has
been a no-op since GCC 8 (and has always been a no-op for
clang, provided only for GCC compatibility).
+ Fix -Wrestrict warning from GCC 16
+ configure.ac: Use $SED consistently to improve portability
to platforms where the installed sed tool isn't just called
`sed`.
+ lemon: Fix bug in -D handling. We were allocating a buffer
based on an unassigned variable. The Xapian build system
doesn't currently use -D so this bug is latent for us but
could result in C compiler warnings during the
+ Remove unused includes of <fstream> and <sstream>.
+ Remove __cplusplus conditional in a header only included
from C++ code.
- changes from version 1.4.31
* API
+ Database::get_spelling_suggestion(): Remove a flawed
optimisation which was rejecting candidate corrections based
only on how many n-grams match.
+ Database::compact(): FULLER compaction now does exactly the
same as FULL.
+ Query: Attempting to construct a pairwise Query from an
operator and two `char*` or `const char*` term names failed
to compile because pointers are iterator types and matched
the template which allows construction from a pair of
iterators which are meant to dereference to give a type
convertible to std::string or Xapian::Query or Xapian::Query*.
We've solved this by only enabling this template for iterators
where sizeof(value_type) is not 1.
+ QueryParser: Improve FLAG_PARTIAL handling for stopwords.
+ RangeProcessor: Don't require prefix/suffix on empty bound
when flag RP_REPEATED is specified (so now `..$10` and
`20kg..` work). Case noted by James Aylett in the
"getting started" guide.
+ ValueRangeProcessor: Don't require prefix/suffix on empty
bound.
+ Fix incorrect container and iterator traits for Xapian API
classes.
* Testsuite:
+ Extend generated tests to cover newer Xapian::Weight subclasses
and Xapian::Utf8Iterator.
* Glass Backend:
+ Compacting a database with corrupt item sizes could try to
copy an item outside of the allocated block. Now we throw
DatabaseCorruptError in this situation.
+ Opening a database table now throws DatabaseCorruptError if
the number of levels is non-zero but the `fake_root` flag
is set.
* Tools:
+ quest: Add --stem-strategy option.
+ quest: List stemming languages in --help.
+ quest: List valid flags/query ops if an invalid one is specified.
* Debug Code:
+ Fix build with `--enable-assertions=partial`.
+ Move an assertion that a pointer is not NULL to before where
we dereference it.
- changes from version 1.4.30
* API:
+ Stem: 1.4.28 changed the English stemmer code to remove an
exception for "skis" which we incorrectly thought wasn't
needed. This was not intended to be a functional change, so
we've restored the exception.
+ Stem: Fix a bug in Snowball's runtime code for decoding
4-byte UTF-8 sequences.
* Portability:
+ Fix instance of undefined behaviour in Database::check()
for glass databases.
- changes from version 1.4.29
* Build System:
+ 1.4.28 had its library version information incorrectly set
- changes from version 1.4.28
* API:
+ Optimise stemming algorithms.
+ Add dutch_porter as alias for current dutch stemmer for
forward compatibility with the next release series where we
will have kraaij_pohlmann as the default dutch stemmer.
* Thu Feb 27 2025 Antonio Larrosa <alarrosa@suse.com>
- update to 1.4.27:
testsuite:
* Fix testcase unsupportedcheck1 for --disable-backend-remote. Reported by
Matthieu Gautier in #832.
* Merge testcases unsupportedcheck1 and stubdb9 which are essentially the same
testcase!
build system:
* Fix build with --disable-backend-chert. Patch from Matthieu Gautier in #832.
portability:
* Add missing include of <cerrno> to fix build failure on macOS 15.
- update to 1.4.26:
API:
* Weight: Document that Weight statistics DOC_LENGTH_MIN, DOC_LENGTH_MAX and
WDF_MAX are for the shard rather than the whole database. Usually this is
what we want as with a sharded database it gives tighter bounds and so better
match optimisation, but it does make them unsuitable for uses such as
calculating a suitable offset to add to every get_sumextra() to allow
implementing a weighting formula which can give a negative term independent
weight contribution. This case will be addressed in the next release series
which also provides bounds such as DB_DOC_LENGTH_MIN which are for the whole
database.
* LMWeight: This class was meant to implement the "Language Model" Weighting
scheme, but we've discovered the implementation was incorrect and fixing it
requires ABI-incompatible changes. For 1.4.x we need to leave it in place so
as not to break existing code, but it's now deprecated and we recommend
avoiding using it. It will be removed in the next release series and
replaced with new separate classes implementing Language Model weighting with
each smoothing. Thanks to Sourav Saha for reporting this problem.
* PL2PlusWeight: Fix bug in implementation of formula. Our variable mean is
1/lambda_t from the PL2+ paper, so we need to check mean>1 for lambda_t<1 but
we were actually checking mean<1 instead. The result of this is that PL2+
actually returned a zero weight unless the term occurred frequently enough in
the collection.
* TradWeight::get_maxpart() no longer forces the wdf_max value to be at least
one. We used to do this so that a non-existent term in the query would cause
it not to achieve 100%, but now we calculate percentages based on the number
of matching subqueries, and it is more natural for a non-existent term to get
zero weight (ditto for a term which always has wdf 0). This was already
addressed for BM25Weight in 1.2.1 back in 2010.
* Enquire::set_expansion_scheme(): Add "prob" as new preferred name for
probabilistic query expansion, with the previous "trad" still being accepted
for now.
* QueryParser::set_prefix() and set_boolean_prefix(): Allow an optional
trailing `:` on the field name. This makes the API here more consistent with
ranges, where you need to include the `:` if you want one. See #720.
testsuite:
* Catch and report if a testcase causes signal SIGPIPE.
* Suppress valgrind errors about calling memmove() with overlapping source and
destination (which is valid, valgrind is just confused when memcpy() and
memmove() share an implementation).
* Add more testing of weighting schemes.
* Mark checkstatsweight3 with a sharded database as XFAIL (expected to fail).
This testcase was previous not run for sharded databases, with a FIXME
comment noting this. Investigating shows it's due to a bug where we use the
shard's termfreqs rather than those for the whole database for an expanded
wildcard, but this seems complex to fix.
matcher:
* Fix minor wildcard weighting bug spotted while reading the code. We were
returning too high a value from the first call to get_maxpart() in some
cases. Mostly this just means the matcher continue working when it could
have stopped, but it will also cause MSet::get_termweight() to return a
higher value than the actual known upper bound.
glass backend:
* Simplify file descriptor handling for lock files on Unix-like platforms
which don't support OFD locks. This eliminates corner cases where we
could end up with file descriptors without close-on-exec set in the main
process.
remote backend:
* xapian-tcpsrv: Use _exit() instead of exit() to end child processes which
avoids the risk of duplicated output from stdio buffers getting copied by
fork() then flushed in both processes.
* Simplify file descriptor handling when launching prog remote.
inmemory backend:
* Fix bug adding posting entries.
build system:
* Improve probe for -Bsymbolic-functions. MSVC doesn't support this flag, but
it only emits a warning when it is used and that warning didn't match any of
the patterns we already check for so we were detecting it as supported.
* Report result of probe to determine compiler support for -Werror or
equivalent.
documentation:
* Improve MSVC build instructions. Thanks to Baran Demir for feedback.
* Improve formatting of stat_flags API documentation.
* sorting.rst: Replace custom weighting scheme documentation with a link to the
more complete equivalent in "Getting Started with Xapian".
* remote.rst: Update to reflect that user metadata is fully supported (since
1.2.4).
portability:
* Fix to compile as C++20 and C++23.
* Resolve SIGPIPE issues on NetBSD, which were causing testcase keepalive1 to
fail. These seem to be due to SO_NOSIGPIPE not working correctly there so
we now use MSG_NOSIGNAL instead for NetBSD.
* Include <errno.h> for sys_errlist. We already do this for the configure
check but were failing to when actually using sys_errlist, which probably
affects at least NetBSD.
* configure: Fix clang detection which wasn't working when configure determined
a -std=X option was needed to get C++11 support. The obvious symptom was
that --enable-werror wouldn't add -Werror.
* configure: NetBSD automatically pulls in library dependencies, so set
link_all_deplibs_CXX=no there.
* Avoid using sprintf() if snprintf() is available, even in cases where the
output size is bounded, to avoid deprecation warnings on macOS. For 1.4.x
we still fall back to sprintf() to avoid a point release breaking support
for any platform still lacking snprintf().
* Stop linking with --enable-runtime-pseudo-reloc. We were requiring this for
cygwin and mingw, but from the documentation it should only be needed for a
library which exports data symbols, which we don't do, and the build works
without it.
* Use `override` for subclassing functors. This is good practice as it gives a
clear compile error if we have to change the signature of an virtual method
on such a functor. See #830.
* Avoid redefining MSVC-specific macros if they are already defined. This
avoids an MSVC warning and potential for the code to be ill-formed if the
user defines these macros with a value other than 1. Patch from A. Jiang
(https://github.com/xapian/xapian/pull/334).
- update to 1.4.25:
API:
* MSet::get_eset(): Don't fetch the collection frequency for each term unless
we're using the Bo1EWeight expansion scheme which actually needs it. In a
simple test this reduced the time taken to do a search and generate expand
terms by a third. Partly addresses #264.
* QueryParser::parse_query(): Fix parse error when using FLAG_CJK_NGRAM (aka
FLAG_NGRAMS) with a query string which has non-CJK followed by whitespace,
CJK, and more non-CJK. Patch from Robert Stepanek
(https://github.com/xapian/xapian/pulls/331).
testsuite:
* unittest: Improve sparse file detection by using SEEK_HOLE, which is
specified by POSIX and seems to be widely supported. On platforms without it
or on an FS with a > 128K block size we will skip the tests involving a 4GB
file, but that's acceptable. On ZFS st_blocks reports the number of blocks
after compression and also lags behind when data has only been committed to
the journal, which means our previous check based on st_blocks couldn't be
made to work without potentially falsely detecting sparse file support.
Fixes #823, reported by someplaceguy.
* apitest: Enable adddoc2 and adddoc5 testcases for sharded databases. We
now just skip the TermIterator::get_termfreq() checks in this case.
glass backend:
* Check Btree level value from disk is in range, which avoids potential out of
range access on corrupt database. Fixes #824, reported by group13.
* Reject invalid blocksize read from corrupted version file. Throw
DatabaseCorruptError if value is out of range or not a power of two.
* Optimise allterms iteration. Most terms don't contain any zero bytes, and
for such terms the key for the first chunk in the termlist table is just the
termname so no decoding is needed when advancing the iterator. This
optimisation is 8.4% faster in a simple test of iterating allterms via
xapian-delve.
* Compaction of an empty non-optional table now gives an empty output, whereas
previous it was one block in size (8K by default). This isn't important in
general as the non-optional tables are not likely to be empty in a real
database, but it's helpful for making small test database and it seems weird
that compaction would make a database much larger in percentage terms in this
edge case.
chert backend:
* Check Btree level value from disk is in range, which avoids potential out of
range access on corrupt database. Fixes #824, reported by group13.
build system:
* configure: DragonflyBSD automatically pulls in library dependencies, so set
link_all_deplibs_CXX=no there.
documentation:
* Document allterms_begin() and termlist_begin() iteration order. Thanks to
Eric Wong for querying this.
* Document TermIterator::get_termfreq() quirk. In the case of a TermIterator
from termlist_begin() on a Document from a sharded database, you get term
frequencies from just the shard. Fixes #423
portability:
* Support building on platforms without AI_NUMERICSERV (e.g. macOS 10.5).
Patch from Sergey Fedorov.
- update to 1.4.24:
testsuite:
* apitest: Add coverage that docids generated by replace_document() don't wrap
to nomoredocids1 testcase.
* unittest: Improve block file functions unit test which were (unintentionally)
trying to test with a 4TB sparse file, which not all platforms support. A
file just over 4GB is enough to test what we want, and if we trying to create
one fails with errno EFBIG, indicating the file size is too large, we now
skip the rest of the testcase.
* unittest: Catch Xapian::Error exceptions and rethrow the std::string returned
by get_description() as the utestsuite harness doesn't know about
Xapian::Error so was confusingly reporting it as "UNKNOWN EXCEPTION".
* The testsuite no longer reports NULL as the address associated with a
signal when running on a platform without both sigaction() and SA_SIGINFO.
matcher:
* Reorder fields in each MSet entry to avoid structure padding on x86-64
probably other 64-bit platforms. This reduces the memory needed to hold an
MSet by 8 bytes per entry on such platforms.
glass backend:
* Eliminate unnecessary memory allocations. When committing changes, we were
allocating blocks for all possible levels of the built-in cursor in each
writable table, even those levels that weren't in use.
The worst case is a really small database with all optional tables existing
which would have 54 unused allocations of blocksize + 8 bytes, which with the
default 8K block size is ~432KB per WritableDatabase; if you explicitly ask
for 64K block size it'll be ~3.4MB.
For a more typical WritableDatabase it's probably going to be more like half
these numbers.
build system:
* Add --enable-werror configure option.
* configure: Only auto-enable -D_FORTIFY_SOURCE=2 if it works without
additional libraries and remove the hard-coded block against using it
on mingw. Mingw-w64 v11.0.0 eliminated the requirement to link with -lssp
and with this change we now auto-enable -D_FORTIFY_SOURCE=2 for it.
portability:
* We now avoid triggering SIGPIPE in library code on most platforms.
On Unix-like platforms we want to avoid generating SIGPIPE when writing to a
socket when the other end has been closed since signals break the
encapsulation of what we're doing inside the library - either user code would
need to handle the SIGPIPE, or we set a signal handler for SIGPIPE but that
would handle *any* SIGPIPE in the process, not just those we might trigger,
and that could break user code which expects to trigger and handle SIGPIPE.
We don't need SIGPIPE since we can check errno==EPIPE instead (which is
actually simpler to do).
It seems all current Unix-like platforms now support SO_NOSIGPIPE or
MSG_NOSIGNAL, so currently we just fall back to setting SIGPIPE to SIG_IGN.
If there are actually current platforms which have SIGPIPE without
SO_NOSIGPIPE or MSG_NOSIGNAL then we can look at other ways to avoid
generating the signal.
* Avoid MSVC warning C4312 which is a reasonable warning in general, but in
this case we checked that the value wasn't truncated when cast to an int.
* Use TEST_EQUAL_DOUBLE in netstats1 testcase which fixes testcase failure on
FreeBSD.
* Address GCC13 -Wredundant-move warnings. In 1.4.10 we added std::move()
here to address clang warnings from -Wreturn-std-move (enabled by -Wall).
Just removing the std::move() reintroduces those warning with clang 8 and
clang 11 (but not clang 13 or later) but changing to apply a static_cast
to the returned type seems to make all versions of both compilers happy.
* Fix build with UCRT64 variant of mingw-w64 by stopping defining
__MSVCRT_VERSION__ by default. It looks like doing so hasn't been needed
since 2015.
* Add workaround for testsuite failures under Wine where attempting to unlink a
stub file sometimes fails with errno == EACCES and _doserrno ==
ERROR_SHARING_VIOLATION. This is what you'd get if the file was still open,
but we've already closed it. Sleeping for a second and retrying makes it
work, so we now do that. It'd be better to get to the bottom of what's going
on, but I've run out of ideas and this workaround is only in the testharness
at least.
debug code:
* xapian-inspect:
+ `goto` and `until` now go to the entry *after* the specified key if there's
no exact match, which seems more natural.
+ New `count` command. This is actually just the same as `until` which
already reports a count of the number of entries advanced by, except that
`count` suppresses printing each entry.
- update to 1.4.23:
API:
* Add `FLAG_NGRAMS` as a preferred new alias for `FLAG_CJK_NGRAM` and
`SNIPPET_NGRAMS` as a preferred new alias for `SNIPPET_CJK_NGRAM`.
In the next release series these features have been expanded to cover many
more languages so the "CJK" in the name has become inaccurate as it stands
for "Chinese, Japanese and Korean").
* Database::check(): Improve the exception message for an empty filename from
"Failed to rewind file descriptor -1 (Bad file descriptor)" to "Couldn't find
Xapian database or table to check (No such file or directory)".
testsuite:
* The test harness now supports generated databases for all backends and
all testcases which can use generated databases now do, which together
improve test coverage as we now run many testcases under more backends.
Generated databases can also be cached, which helps speed up the test
suite.
* Remove some testcases which are now redundant with other testcases or
no longer useful for other reasons.
* Add regression test for #781, reported by Germán M. Bravo. This bug was
fixed 4 years in 1.4.12 but a clean regression test only became possible
thanks to changes in this release.
* The test harness would attempt to throw a Xapian::Database (rather than
Xapian::DatabaseError) if it failed to rename a temporary database to its
final name. This would fail because there wasn't a database called "rename
failed". Reported by stark3y on #xapian.
* apitest: Fix exceed32bitcombineddb1 testcase (which only runs with
- -enable-64bit-docid).
* apitest: Fix nomoredocids1 when configured with --enable-64bit-docid.
* Add testcase for removal of positions for replaced doc (regression test for
bug in git master not present in 1.4.x).
* unittest: Unit test block file functions
* Stop using std::endl in tests since this seems to be C++ best practice
as it causes a flush of the stream, which is rarely actually wanted. Also
often the replacement \n can be combined with a string literal.
* Use Xapian::docid for document ids in testcases. Using `int` or `size_t`
works, but is less correct and can trigger compiler warnings because not all
values are representable.
matcher:
* BM25PlusWeight: With some parameter combinations we were requesting stats we
didn't actually need. Confirmed with Vivek Pal on IRC.
glass backend:
* Avoid unnecessary copying of data when adding an item to a B-tree table which
should speed up indexing a bit.
* xapian-check: If the first chunk for a term is a continuation chunk, the
affected term was missing from the error message.
* xapian-check: We now report the document id as context in many more error
messages.
chert backend:
* Fix wdf upper bounds used when search a modified chert-format
WritableDatabase object. A bug introduced in 1.4.19 meant we were using the
wdf upper bounds from the last committed version of the database. This bug
could cause assertion failures when configured with --enable-assertions.
remote backend:
* Fix thread-safety issue starting remote prog server. Previously we did some
memory allocation in the child process after fork() but before we exec-ed the
specified program, but in a multi-threaded program (which libxapian might be
used in) it's only safe to call async-signal-safe functions in the child
process after fork() until exec, and malloc, etc aren't async-signal-safe.
* If we failed to open /dev/null in the child process while starting a remote
prog server, we would try to throw an exception. That's not going to work
well so now we just call `_exit(-1)`.
inmemory backend:
* Throw exception on docid overflow like we do in other backends.
build system:
* configure: When probing for socklen_t or equivalent include the same headers
as we do in the code to reduce the risk of configure deciding to use
socklen_t but it not getting defined in the code.
* configure: When probing if a particular compiler or linker option is
supported, we were relying on the compiler exit status but some compilers
only warn about unknown options. We now inspect the compiler's stderr
output to try to detect such cases.
* configure: Avoid compiler warning during GCC version check when compiler
needs an option to enable C++11 support.
* Avoid running pwd since the directories we need are available in automake
variables.
documentation:
* Suggest protocol buffers for structured document data. Fixes #53.
* Clarify documentation for release() methods.
* Fix typo "shared database" to "sharded database" in API docs.
* Document that transactions aren't atomic across shards.
tools:
* xapian-progsrv,xapian-tcpsrv: Support multiple DBs with --writable.
* xapian-tcpsrv: Fix default timeouts in --help output which have been reported
as the name of the constant rather than its value since 1.3.3.
* xapian-tcpsrv: When --one-shot is specified, don't do the usual test open of
the specified database(s) as it doesn't really seem useful in this case. The
test harness uses --one-shot so this reduces overhead when running remote
tests.
* Stop using std::endl in tools since this seems to be C++ best practice
as it causes a flush of the stream, which is rarely actually wanted. Also
often the replacement \n can be combined with a string literal.
portability:
* Don't pass mode to open when it's unused as this triggers "missing O_CREAT or
O_TMPFILE?" warnings when compiling for Android.
* Stop using INFINITY macro. If the implementation supports floating point
infinities then HUGE_VAL gives us infinity as a double directly. If not,
then it's the maximum finite value of a double.
* Don't auto-enable _FORTIFY_SOURCE on mingw or mingw-w64. Enabling
_FORTIFY_SOURCE on newer mingw-w64 requires linking with -lssp so we
attempted to stop automatically enabling it there in 1.4.19 but this fix
didn't actually work. Trying to get this to work automatically has proved
difficult and I couldn't find evidence that _FORTIFY_SOURCE was actually
supported on mingw. If it is, enabling manually will still work.
* Fix mingw32 build with C++17 compiler, which ends up with std::byte
conflicting with byte typedefs in system headers, due to us having `using
namespace std;` in some of our internal headers. Switch the ones which
are causing problems to more targetted `using std::string;`, etc instead.
* Fix WIN32 build with --disable-backend-remote which was failing because we
were always trying to build common/socket_utils.cc which fails because
SOCKLEN_T hasn't been probed. Fixes #821, reported by mgautier.
* soaktest: Use C++11 <random> which is more portable than random().
* In WIN32 builds, pass the program pathname separately to CreateProcess()
which is apparently more robust if the program pathname contains spaces.
* Stop trying to set Microsoft-specific SO_EXCLUSIVEADDRUSE option on our
listening sockets. It's not possible to set both SO_REUSEADDR and
SO_EXCLUSIVEADDRUSE so this call will always fail with WSAEINVAL, but we
were ignoring these errors because SO_EXCLUSIVEADDRUSE required admin
privileges in older OS versions.
* Suppress MSVC deprecation warning for GetVersionEx since none of the
suggested replacements seems to actually provide the functionality we are
using from it.
* Fix some warnings from MSVC in the fallback code for overflow-checked
arithmetic.
* Support Enquire::set_time_limit() on GNU Hurd since Hurd now implements
timer_create().
* Remove lingering traces of IRIX support as it's been dead for many years.
debug code:
* Fix build failure with --enable-assertions due to incorrect variable name in
assertion. Patch from Alexei Kharchev in
https://github.com/xapian/xapian/pull/327.
* Fix GCC warning with --enable-log.
* Fix debug logging for 3 GlassDatabase methods to log their parameter.
* Add a mechanism to support debug logging templated return types containing
commas. This was added to fix a build failure on master with --enable-log
reported by ttyS3.
* Thu Aug 22 2024 ming li <mli@suse.com>
- update to 1.4.22:
* Expand canceltransaction1 to test value changes are rolled back.
* Minor optimisations to DPHWeight and TfIdfWeight weighting formulae
calculations.
* Optimise LatLongDistancePostingSource to avoid pow() call on each document
with default k2 setting.
* Fix bug in recovery from WritableDatabase::commit() failing.
* configure: Enable -fno-math-errno if supported. We don't make use of maths
function setting errno and if we tell the compiler that it can optimise them
better in some cases.
* INSTALL: Document assumptions about platform features
* INSTALL: Add section on clang version requirements.
* Thu Sep 29 2022 Dirk Müller <dmueller@suse.com>
- update to 1.4.21:
* Stop trying to check for incompatible C++ ABI between the compiler used to
build xapian-core and the compiler used to build code using xapian-core.
* Fix new warnings from GCC 12.
* Avoid undefined value use when unpacking a key in a corrupted glass docdata
table. We now skip further checks on the entry in this case.
* Merge allocations in MSVC directory reading compatibility code so we can
allocate in a single malloc() call.
* Add accept() wrapper which checks an assumption that Microsoft's SOCKET type
only actually holds 32 bit values even in 64 bit platforms and throws an
exception if violated.
* Eliminate a use of sprintf.
* Squash some unhelpful MSVC deprecation warnings.
* Declare dummy invalid parameter handler noexcept to fix a warning from MSVC.
* Include <stdlib.h> in configure check for sys_errlist as that's where it is
with mingw and MSVC.
* Sun Jul 17 2022 Dirk Müller <dmueller@suse.com>
- update to 1.4.20:
* Throw DatabaseNotFoundError when the database directory doesn't exist or
when it doesn't contain a Xapian database. Patch from Germán Méndez Bravo
in https://github.com/xapian/xapian/pull/258
* Improve exception message for attempting to remove an empty term (the
exception type is still InvalidArgumentError). Reported by David Bremner.
* Optimise when a value range is a superset of the slot bounds but the value
slot frequency is not equal to the document count by replacing the lower
bound with an empty string to make the bounds check very cheap.
* Avoid creating a PostList tree for an empty shard. This avoids pointless
work in an uncommon case, but also by handling this up front the code in
PostList subclasses for query operators can assume the shard isn't empty
which simplifies the code in several places.
* Remove lingering handling for database backends without slot bounds since
all backends have been required to support these since 1.4.11.
* Fix collection frequency estimates for positional operators. This affects
the weighting of positional operators in subqueries of OP_SYNONYM with
weighting schemes which use the collection frequency.
* xapian-check: Test decompress data in the spelling and synonym tables.
We don't have structure checking for these tables, but we can at least fetch
each entry and check for decompression problems.
* Improve error if a block is detected as overwritten in WritableDatabase.
Drop "are there multiple writers?" as it's rarely a useful question to ask
since we started using fcntl() locking as it's now very hard to get multiple
concurrent writers on a database. Instead suggest running xapian-check,
which is probably the best next step for a user who hits this problem.
* Wed Jan 19 2022 Dirk Müller <dmueller@suse.com>
- update to 1.4.19:
* New QueryParser::FLAG_NO_POSITIONS flag. With this flag enabled, any query
operations which would use positional information are replaced by the nearest
equivalent which doesn't (so phrase searches, NEAR and ADJ will result in
OP_AND). This is intended to replace the automatic conversion of OP_PHRASE,
etc to OP_AND when a database has no positional information, which will no
longer happen in the release series after 1.4.
* Give a compile error for code which adds a Database to WritableDatabase.
Prior to 1.4.19, this compiled and effectively created a "black-hole" shard
which quietly discarded any changes made to it.
In 1.4.19 it's still possible to perform this operation by assigning the
WritableDatabase to a Database first, which is harder to fix. This case
throws an exception on git master where it's easier to address.
* Fix TermIterator::skip_to() with sharded databases which sometimes was
failing to advance all the way to the requested term. Uncovered while
addressing warning from GCC's -Wduplicated-cond, reported by dcb in #816.
* Clamp edit distance to one less than the length of the word we've been asked
to correct, which makes the algorithm we use more efficient. We already
require suggestion to have at least one character in common, so the only
change to suggestions is we'll no longer suggest corrections which are
twice as long or longer even if the edit distance would allow it, which
seems like an improvement in itself.
* Minor optimisation expanding wildcards.
* PostingIterator::get_description(): For an all-docs iterator on a glass
database, get_description() would call get_docid() which isn't valid to
do once the iterator has reached the end.
* Expand allterms test coverage.
* Fetch wdf upper bound from postlist which avoids an extra postlist table
cursor seek per weighted query term, and also means we now use a per-shard
wdf upper bound for local shards which will in typically give a tighter
weight upper bound which will tend to make various other matcher
optimisations more effective. Eric Wong reported this speeds up a
particularly slow case from ~2 minutes to ~3 seconds.
* Avoid triggering a pointless maximum weight recalculation if an unweighted
child of a MultiAndPostList prunes.
* Only check if the database has positional information when the query
uses positional information. This should help improve notmuch delete
performance. Thanks to andreas on #notmuch for analysis of the problem.
* Optimise Glass::Inverter::has_positions(). Use const auto& instead of just
auto for the loop variables. Reported to be faster by andreas on #notmuch.
* Cache result of Glass::Inverter::has_positions() since calculating it is
potentially very expensive, while maintaining a cached answer is very cheap.
* Add missing closing parenthesis to reported remote prog context, which has
been missing since this code was first added over 20 years ago!
* Tue Jan 19 2021 Dirk Müller <dmueller@suse.com>
- update to 1.4.18:
* QueryParser::FLAG_ACCUMULATE: New flag. Previously the unstem and stoplist
data was always reset by a call to QueryParser::parse_query(), which makes
sense if you use the same QueryParser object to parse a series of independent
queries. If you're using the same QueryParser object to parse several fields
on the same query form, you may want to have the unstem and stoplist data
combined for all of them, in which case you can use this flag to prevent this
data from being reset.
* QueryParser::unstem_begin(): Eliminate unnecessary copying of the data.
* Fix typo in Swedish stopword list, syncing change made to Snowball by Daniel
Gómez Villanueva.
* Remove some French stop words with other meanings, syncing change made to
Snowball by PhilippeOuellet.
testsuite:
* Run testcase testlock4 using backend chert, not just using glass
* Skip testcase testlock4 on platforms that don't allow us to implement
Database::locked() (which notably include GNU Hurd and Microsoft Windows).
documentation:
* List DB_NO_TERMLIST in the WritableDatabase constructor API documentation
where we already list the other DB_* constants.
portability:
* Eliminate single use of std::mem_fun() which was deprecated in C++11 and
removed in C++17. Reported by Mateusz Pusz in #806.
* Add missing includes for std::numeric_limits<>. Reported by stac47 in #805.
* Work around mingw.org header issue. MSVC seems to implicitly include
<winerror.h> but mingw.org's headers don't, leading to ERROR_PIPE_CONNECTED
not being defined. Fixes https://github.com/xapian/xapian/pull/318, reported
by Alex Sandro.
* Suppress MSVC warnings about possible loss of data. The values involved are
the number of set bits in a value of integer type, so these warnings are
bogus.
* Include <sys/types.h> for size_t and off_t, which is the appropriate header,
and needed with Android's bionic libc. Patch from Matthieu Gautier.
* Use a temporary file for the Doxygen configuration to work around Doxygen
1.8.19 bug which truncates a config file read from stdin to 4096 bytes
* Thu Aug 27 2020 Antonio Larrosa <alarrosa@suse.com>
- Update to 1.4.17:
+ API:
* Database::get_average_length(): Add this as an alias for Database::get_avlen().
In git master we've added this as a preferred new name - adding it to 1.4.x too
will make it easier for users to update to using this.
* Database::get_spelling_suggestion(): Optimise edit distance initialisation
loop to significantly reduce the cost of a typical edit distance calculation.
* Fix query expansion on sharded databases. The mechanism for passing in which
shard a TermList is from wasn't hooked up and as a result we'd always think
it's from the first shard, meaning the statistics would be wrong and that our
suggested terms may not have been as good as they should be in this
situation.
* Enquire::get_eset(): Use string::compare() to avoid 1/3 of the string compares
on average.
+ documentation:
* Update doxygen HTML headers and footers to resolve issues with some
interactive features of the API docs not working. Reported by Enrico Zini.
* Stop specifying obsolete doxygen settings PERL_PATH and MSCGEN_PATH.
* Clarify API docs for MSet::get_termfreq() to make it clear that this
considers all documents in the database, not only those that matched the
searched (it would sometimes be useful to be able to report the number of
occurrences of a term in the matched documents, but it's not something we
currently keep track of). Reported by Tadeusz Sośnierz and Peter Salomonsen.
* Sat Aug 15 2020 Dirk Mueller <dmueller@suse.com>
- update to 1.4.16:
* MSet::snippet(): The snippet now includes trailing punctuation which carries
meaning or gives useful context. See
https://github.com/xapian/xapian/pull/180, reported by Robert Stepanek.
* MSet::snippet(): Fix segfault generating snippet from default-constructed
MSet. This probably isn't something you'd typically do, but it shouldn't
crash. Found during extended testing of #803 (which only affected git
master) which was reported by Robert Stepanek.
* Remove trailing full stop from exception messages. We conventionally don't
include one, but a few cases didn't follow that convention.
testsuite:
* Replace direct use of ftime() which gives deprecation warnings with recent
mingw. Reported by srinivasyadav22.
matcher:
* Fix segfault in rare cases in the query optimiser. We keep a pointer to the
most recent posting list to use as a hint for opening the next posting list,
but the existing mechanism to take ownership of this hint had a flaw. We now
invalidate the hint in situations where it might be indirectly deleted which
is safe, but somewhat conservative.
* Improve the optimisation of an always-matching OP_VALUE_GE to also take
effect when the value slot's lower bound is equal to the limit of the
OP_VALUE_GE. Patch from boda sadalla.
glass backend:
* Report the correct errno value if commit() fails. We were potentially
reporting ENOENT from an unlink() call cleaning up a temporary file prior to
throwing the exception instead.
documentation:
* Fix missing menus in API documentation. Newer doxygen generates .js files
which we also need to distribute and install. Reported by sec^nd on #xapian.
* Note OP_FILTER ignored subquery bug fixed in 1.4.15 as present in 1.4.14 and
older.
portability:
* Use our own autoconf cache variable namespace (xo_cv_ prefix instead of
ac_cv_) to avoid colliding with standard autoconf macro use if config.site or
a shared config.cache is used. The former case caused a build failure for
the OpenBSD port with 1.4.15, reported by Lucas R.
* Use clock_gettime() and nanosleep() under modern mingw as these allow higher
precision than what we previously used.
* Wed Apr 29 2020 Dominique Leuenberger <dimstar@opensuse.org>
- Update to version 1.4.15:
+ API:
* Database::check(): Fix checking of replication changesets.
This reverts a change incorrectly made in 1.3.7.
* Database::locked(): Return false instead of true for a closed inmemory DB.
* Database::commit(): If commit() failed with an exception while trying to add
pending changes (e.g. InvalidArgumentError due to a long term containing zero
bytes) then a subsequent commit() on the same object would throw the same
exception. Now we clear the pending changes in this situation (like we
already did for failure at other stages in the commit). This bug remains
unfixed for the chert backend as it's harder to fix there and the effort to
fix it and extra risk of breakage don't seem justified for a backend we
recommend people migrate away from.
* QueryParser::parse_query(): Optimise parsing of multi-word synonyms.
+ Testsuite fixes.
+ matcher:
* Hoist positional check above OP_FILTER.
* Handle OP_FILTER with more than two subqueries correctly. Previously we'd
only check the first two subqueries in some situations.
+ remote backend:
* For a remote WritableDatabase, the client now keeps track of whether there
are pending changes, and if there aren't then we now do nothing for commit()
or cancel() calls. In particular this saves a message exchange when the
WritableDatabase destructor is called when changes have already been
committed with an explicit call to commit() (which is what we recommend
doing, since with an explicit call to commit() you get to see any exception
which gets thrown).
* When closing a remote prog WritableDatabase, previously an exception could
leave the remote connection open with the remote server running, and we'd
then wait for the specified timeout before closing the connection. Now we
close the connection before letting the exception propagate.
* Don't swallow exceptions from Database::close() on a remote database. If
we aren't in a transaction and so try to commit() and that fails then
previously the caller would have no indication of the failure.
* Fix handling the reported term weight when remote shards are searched.
Fixes 5 XFAILs in the testsuite.
* Add missing space to mismatching protocol versions error message.
+ build system:
* Fix to build when configured with --disable-backend-remote, broken by changes
in 1.4.14. Fixes #797, reported by Дилян Палаузов.
* The clang and icc compilers both define __GNUC__, which led our ABI mismatch
message to report them as "g++" with a bogus version (the version of GCC that
these compilers advertise themselves as, which for clang is always 4.2.0) -
now we report clang++ or icc along with the actual version of that compiler.
+ updated documentation.
/usr/bin/xapian-config /usr/include/xapian /usr/include/xapian.h /usr/include/xapian/attributes.h /usr/include/xapian/compactor.h /usr/include/xapian/constants.h /usr/include/xapian/constinfo.h /usr/include/xapian/database.h /usr/include/xapian/dbfactory.h /usr/include/xapian/deprecated.h /usr/include/xapian/derefwrapper.h /usr/include/xapian/document.h /usr/include/xapian/enquire.h /usr/include/xapian/error.h /usr/include/xapian/errorhandler.h /usr/include/xapian/eset.h /usr/include/xapian/expanddecider.h /usr/include/xapian/geospatial.h /usr/include/xapian/intrusive_ptr.h /usr/include/xapian/iterator.h /usr/include/xapian/keymaker.h /usr/include/xapian/matchspy.h /usr/include/xapian/mset.h /usr/include/xapian/positioniterator.h /usr/include/xapian/postingiterator.h /usr/include/xapian/postingsource.h /usr/include/xapian/query.h /usr/include/xapian/queryparser.h /usr/include/xapian/registry.h /usr/include/xapian/stem.h /usr/include/xapian/termgenerator.h /usr/include/xapian/termiterator.h /usr/include/xapian/types.h /usr/include/xapian/unicode.h /usr/include/xapian/valueiterator.h /usr/include/xapian/valuesetmatchdecider.h /usr/include/xapian/version.h /usr/include/xapian/visibility.h /usr/include/xapian/weight.h /usr/lib/cmake /usr/lib/cmake/xapian /usr/lib/cmake/xapian/xapian-config-version.cmake /usr/lib/cmake/xapian/xapian-config.cmake /usr/lib/libxapian.la /usr/lib/libxapian.so /usr/lib/pkgconfig/xapian-core.pc /usr/share/aclocal/xapian.m4
Generated by rpm2html 1.8.1
Fabrice Bellet, Fri Oct 9 00:37:39 2026