Source: xapers
Version: 0.9.0-4
Severity: normal
Xapian 2.0.0 is close to release - currently we're on the second release
candidate:
https://lists.xapian.org/pipermail/xapian-discuss/2026-March/thread.html
This is packaged in Debian experimental (versioned as 1.5.1-1) and the
CI run for xapian-bindings shows it breaks xapers:
https://ci.debian.net/packages/x/xapers/unstable/arm64/69257709/
I had a quick look at the xapers code and it's still using the
xapian.NumberValueRangeProcessor class which was deprecated in 1.4.x and
removed in 2.0.0.
The replacement is xapian.NumberRangeProcessor which will work in 1.4.x
too. I've attached an entirely untested patch.
Cheers,
Olly
-- System Information:
Debian Release: forky/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.18.10+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- xapers/database.py~ 2026-03-07 09:52:43.243317673 +1300
+++ xapers/database.py 2026-03-07 09:52:47.758132090 +1300
@@ -174,8 +174,8 @@
# add value facets
for name, facet in self.NUMBER_VALUE_FACET.items():
- self.query_parser.add_valuerangeprocessor(
- xapian.NumberValueRangeProcessor(facet, name+':')
+ self.query_parser.add_rangeprocessor(
+ xapian.NumberRangeProcessor(facet, name+':')
)
# register known source prefixes
