[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#837630: transition: xapian-core



Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

I'd like to transition the archive to Xapian 1.4 before the next
release.

There are packages of xapian-core 1.4.0 in experimental.  I maintain
xapian-bindings and xapian-omega, and packages of 1.4.0 for those are
also in experimental.  All three packages have built on all release
architectures:

https://buildd.debian.org/status/package.php?p=xapian-bindings+xapian-core+xapian-omega&suite=experimental

I've test rebuilt the other reverse dependencies and they all built
cleanly with the exception of:

 * pinot - this FTBFS in unstable due to GCC 6 (RC bug #812165) and
   (as I've noted in that bug) when I patch that and rebuild against
   xapian-core 1.4.0 the resulting binary segfaults when run, due to
   something which appears to be related to symbol mangling.  Since
   Xapian is GPLv2+ and pinot also links to openssl the package
   doesn't appear to be distributable anyway (RC bug #833692), and
   pinot has already been removed from testing, so this doesn't seem
   like a blocker for the transition.

 * libsearch-xapian-perl - this needs a patch for compatibility with
   xapian-core 1.4.  I have just completed such a patch, which I'm
   going to apply upstream, so depending when the transition is
   schedule we can either apply the patch or package a newer upstream
   version if one has been released by then.  I'm an uploader for this
   package, so can easily do either.

The auto-generated tracker looks good to me:
https://release.debian.org/transitions/html/auto-xapian-core.html

Cheers,
    Olly

Attachment: signature.asc
Description: PGP signature


Reply to: