Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Upstream xapian-core 1.4.6 added C++11 move constructors and move
assignment operators when code using the xapian API is built with a
C++11 or newer compiler, which GCC in unstable is by default.
The compiler will very likely find places to use the move versions
implicitly, so a package built against libxapian-dev >= 1.4.6-1 is
unlikely to work with libxapian30 << 1.4.6.1 due to missing symbols.
We'll often get away with this because the packages will generally
be upgraded together, so that's probably why there's not been a flood
of reports. This breakage was reported by a user who tried to
perform a large upgrade by separately upgrading aptitude first:
https://bugs.debian.org/910110
1.4.7-4 adds the appropriate dependency to libxapian30.shlibs, so any
packages built against libxapian-dev 1.4.6-1 to 1.4.7-3 inclusive should
be rebuilt so they automatically depend on libxapian30 (>= 1.4.6-1~)
instead of just libxapian30.
I've extracted a list of such packages based on the buildinfo files on
mirror.ftp-master.d.o (thanks to pabs for suggesting this):
nmu pinot_1.05-2 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw pinot_1.05-2 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu zeitgeist_1.0.1-0.2 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw zeitgeist_1.0.1-0.2 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu maildir-utils_1.0-6 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw maildir-utils_1.0-6 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu baloo-kf5_5.49.0-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw baloo-kf5_5.49.0-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu recoll_1.24.1-3 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw recoll_1.24.1-3 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu plasma-desktop_5.13.5-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw plasma-desktop_5.13.5-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu plasma-workspace_5.13.5-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw plasma-workspace_5.13.5-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu aptitude_0.8.11-3 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw aptitude_0.8.11-3 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu packagesearch_2.7.9 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw packagesearch_2.7.9 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu cyrus-imapd_2.5.11-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw cyrus-imapd_2.5.11-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu akonadiconsole_18.08.1-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw akonadiconsole_18.08.1-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu akonadi-search_18.08.1-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw akonadi-search_18.08.1-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu notmuch_0.28~rc0-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw notmuch_0.28~rc0-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu libsearch-xapian-perl_1.2.25.2-1 . ANY . -m 'Rebuild against libxapian30 with dependency in shlibs'
dw libsearch-xapian-perl_1.2.25.2-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
The new xapian-core was uploaded close to two days ago and has
now built everywhere except kfreebsd-*. I'll recheck in a week in
case there any further binary uploads built against the old xapian-core,
and follow-up with another request if necessary.
Cheers,
Olly
Attachment:
signature.asc
Description: PGP signature