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

Bug#837630: marked as done (transition: xapian-core)

Your message dated Tue, 11 Oct 2016 00:15:28 +0200
with message-id <c3acceae-6eec-7798-47f9-7c0f78dd86ec@debian.org>
and subject line Re: Bug#837630: transition: xapian-core
has caused the Debian Bug report #837630,
regarding transition: xapian-core
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

837630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837630
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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

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


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:


Attachment: signature.asc
Description: PGP signature

--- End Message ---
--- Begin Message ---
On 01/10/16 15:51, Emilio Pozuelo Monfort wrote:
> binNMUs scheduled.

This is done; closing.


--- End Message ---

Reply to: