On 30/09/16 06:53, Olly Betts wrote: > On Thu, Sep 29, 2016 at 09:28:27PM +0100, Olly Betts wrote: >> On Thu, Sep 29, 2016 at 06:55:56PM +0200, Emilio Pozuelo Monfort wrote: >>> On 13/09/16 06:50, Olly Betts wrote: >>>> https://release.debian.org/transitions/html/auto-xapian-core.html >>> >>> Go ahead! >> >> Great, thanks. I have just uploaded xapian-core 1.4.0-2 to unstable. > > Done, and has now successfully built and installed on all release > architectures: > > https://buildd.debian.org/status/package.php?p=xapian-core&suite=sid > >> Assuming that looks good, I'll make sourceful uploads of xapian-bindings, >> xapian-omega and libsearch-xapian-perl. > > All now uploaded and accepted. > >> I'll also retest pinot in case the symbol mangling was due to a mix of >> code compiled with GCC5 and GCC6 - IIRC the ABI has changed in some >> obscure cases, so maybe this is due to one of those. > > I solved this issue - the pinot sources hard code a mangled symbol > string. It doesn't matter for this transition, but I've NMUed pinot > with this and the FTBFS with GCC6 fixed. > >> The rest of the pacakges in the tracker should just need a binNMU. > > For clarity, the following will need binNMUs: > > akonadi-search > aptitude > baloo > khelpcenter > libept > libqapt > maildir-utils > notmuch > recoll > zeitgeist > > And then: > > goplay > packagesearch > synaptic > > I'm in #debian-release - feel free to ping me about anything.
binNMUs scheduled. Emilio
