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 immediately.) -- 837630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837630 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: xapian-core
- From: Olly Betts <olly@survex.com>
- Date: Tue, 13 Sep 2016 16:50:54 +1200
- Message-id: <20160913045054.cf4zbgv3pyszlqno@survex.com>
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, OllyAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Olly Betts <olly@survex.com>
- Cc: 837630-done@bugs.debian.org
- Subject: Re: Bug#837630: transition: xapian-core
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Tue, 11 Oct 2016 00:15:28 +0200
- Message-id: <c3acceae-6eec-7798-47f9-7c0f78dd86ec@debian.org>
- In-reply-to: <[🔎] 3a616878-8a64-fd1b-1d54-b223494b1527@debian.org>
- References: <20160913045054.cf4zbgv3pyszlqno@survex.com> <95766212-8b6c-ad40-cf93-5e83d0803a72@debian.org> <20160929202827.GB19514@survex.com> <20160930045359.nm7ziq55eya4pnms@survex.com> <[🔎] 3a616878-8a64-fd1b-1d54-b223494b1527@debian.org>
On 01/10/16 15:51, Emilio Pozuelo Monfort wrote: > binNMUs scheduled. This is done; closing. Emilio
--- End Message ---