Bug#901015: transition: protobuf
Hi Emilio, On Thu, Oct 11, 2018 at 12:56 PM Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 11/09/2018 09:51, László Böszörményi (GCS) wrote: > > The last package which fails is gazebo which seems to be team > > maintained but it has two NMUs already. There's no bug reported here > > for the protobuf update but upstream aware of it and has a patch[1]. > > This one is not yet tested by me, but the upstream BTS contains a > > comment that's a working fix for gazebo 7.x and the original bug > > report[2] states that the fix is in place for the 8.x and 9.x versions > > as well. If you have time, please file a bug for this to the gazeboo > > source package - but as noted its Debian maintainers are not very > > active. > > Sounds good. Please go ahead with the transition and bump the bugs to serious. Uploaded ProtoBuf with the latest gRPC to Sid. Already built on most release architectures, only mips64el and mipsel have still these in their build queue. Reverse dependencies seems to be updated expect Gazebo. Raised its bug severity[1]. Cheers, Laszlo/GCS [1] https://bugs.debian.org/908854#10
Bug#909288: transition: kdepim 18.08
On 08/10/2018 23:21, Sandro Knauß wrote: > Hey Emilio, > > I uploaded kmailtransport_18.08.1-2 that should build on more archs (as it > makes libkgapi optional). > > hefee > > @pino sorry - I forgotten to pull before starting to work, so your updates > are > not included in the -2. > This transition is blocked on blogilo. Looking upstream to see if there's a fix, I found out that https://userbase.kde.org/Blogilo has a blogilo homepage link that links to http://blogilo.gnufolks.org/ which redirects to https://choqok.kde.org/ Does that mean that blogilo has been superseeded by choqok? If so, should blogilo be turned into an empty transitional package? Also any chance you can look at uploading kopete/exp with a fix for the new libmediastreamer (patch in #890606) to sid? That would help in two transitions. Thanks, Emilio
Re: [Pkg-rust-maintainers] rust-ripgrep 0.9.0-4 MIGRATED to testing
On 12/10/2018 06:40, Ximin Luo wrote: > Ximin Luo: >> Niels Thykier: >>> Ximin Luo: This should not have happened, ripgrep was not ready yet. https://packages.debian.org/source/buster/rust-ripgrep It build-depends on (e.g.) librust-clap-2+color-dev which is a virtual-package provided by https://packages.debian.org/sid/librust-clap+color-dev but this package is not yet in Debian Testing, and no other packages in Debian Testing provide the same virtual package. I wanted to file a bug here https://salsa.debian.org/release-team/britney2 but salsa is down atm. X [...] >>> >>> Hi, >>> >>> From a quick look at the situation, this is expected behaviour as there >>> is only partial support for Build-Depends (please see #903211 comment 10 >>> for details). >>> >>> We are of course happy to improve the documentation[1] on how to make >>> these limitations more obvious. >>> >>> Thanks, >>> ~Niels >>> >>> [1] https://release.debian.org/doc/britney/ >>> Source: docs folder in the britney2 repo >>> >> >> So what's the best way for us the rust packaging team to track these >> situations? Presumably when it's time to release Debian buster these >> situations will still be bugs, but we don't want to have to deal with them >> all at the same time. >> > > Hi, I just wanted to follow up to this - we never got an answer here but it > is still an outstanding issue. For example rust-ripgrep 0.9.0-4 in testing > (buster) is not buildable in testing because it build-depends on rust-clap > which is only in unstable. > > https://packages.debian.org/source/buster/rust-ripgrep > > If you want a more precise description of the issue see > https://github.com/kpcyrd/cargo-debstatus/issues/2 but it seems to me that > you understand it already. Yes, this is an issue in britney, see #599848. For the time being, if you want to know which packages are currently problematic, in order to solve these issues before the freeze, you can look at https://qa.debian.org/dose/debcheck/src_testing_main/index.html e.g. on https://qa.debian.org/dose/debcheck/src_testing_main/1539320405/amd64.html I only see rust-ripgrep matching /rust/. Cheers, Emilio
Bug#910875: transition: x265
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-x265.html x265 bumped its SONAME again and needs a transition. All reverse dependencies build fine against the new version. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: transition: x265
Processing control commands: > forwarded -1 https://release.debian.org/transitions/html/auto-x265.html Bug #910875 [release.debian.org] transition: x265 Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-x265.html'. -- 910875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910878: transition: qtbase-opensource-src
Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition Dear release team, Qt has released a new bugfix release (5.11.2) recently, and we need a transition to get it into unstable. The packages are already prepared in experimental. It is a patch release so it should go smooth compared to minor (5.x.0) releases. As usual, we have two sub-transitions: title = "qtbase-opensource-src"; is_affected = .depends ~ "qtbase-abi-5-11-0" | .depends ~ "qtbase-abi-5-11-2"; is_good = .depends ~ "qtbase-abi-5-11-2"; is_bad = .depends ~ "qtbase-abi-5-11-0"; and title = "qtdeclarative-opensource-src"; is_affected = .depends ~ "qtdeclarative-abi-5-11-0" | .depends ~ "qtdeclarative-abi-5-11-2"; is_good = .depends ~ "qtdeclarative-abi-5-11-2"; is_bad = .depends ~ "qtdeclarative-abi-5-11-0"; Note that we will likely want to do one more transition before Buster release. Namely, one that will switch the default OpenGL version from desktop to OpenGL ES on arm64. We are not yet ready for it, and it will affect more packages (including some that will need NMUs), so we decided to decouple it from this one. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Closing old transition bug
Processing commands for cont...@bugs.debian.org: > close 902263 Bug #902263 [release.debian.org] transition: qtbase-opensource-src Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 902263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910875: transition: x265
Control: tags -1 confirmed On 12/10/2018 17:54, Sebastian Ramacher wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-x265.html > > x265 bumped its SONAME again and needs a transition. All reverse dependencies > build fine against the new version. Go ahead. Emilio
Processed: Re: Bug#910875: transition: x265
Processing control commands: > tags -1 confirmed Bug #910875 [release.debian.org] transition: x265 Added tag(s) confirmed. -- 910875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910610: dnsmasq 2.76-5+deb9u2 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: dnsmasq Version: 2.76-5+deb9u2 Explanation: trust-anchors.conf: include latest DNS trust anchor KSK-2017
Bug#910719: nagstamon 2.0.1-5+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: nagstamon Version: 2.0.1-5+deb9u1 Explanation: address IcingaWeb2 Basic auth issue
Processed: nagstamon 2.0.1-5+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #910719 [release.debian.org] stretch-pu: package nagstamon/2.0.1-5+deb9u1 Added tag(s) pending. -- 910719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nagstamon 2.0.1-5+deb9u1 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #910719 [release.debian.org] stretch-pu: package nagstamon/2.0.1-5+deb9u1 Ignoring request to alter tags of bug #910719 to the same tags previously set -- 910719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dnsmasq 2.76-5+deb9u2 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #910610 [release.debian.org] stretch-pu: package dnsmasq/2.76-5+deb9u1 Added tag(s) pending. -- 910610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dnsmasq 2.76-5+deb9u2 flagged for acceptance
Processing control commands: > tags -1 + pending Bug #910610 [release.debian.org] stretch-pu: package dnsmasq/2.76-5+deb9u1 Ignoring request to alter tags of bug #910610 to the same tags previously set -- 910610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u1.1_source.changes REJECT Processing changes file: dnsmasq_2.76-5+deb9u2_source.changes ACCEPT Processing changes file: linux_4.9.130-1_source.changes ACCEPT Processing changes file: nagstamon_2.0.1-5+deb9u1_source.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_sourceonly.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_all.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_amd64.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_arm64.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_armel.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_armhf.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_i386.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_mips.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_mips64el.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_mipsel.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_ppc64el.changes ACCEPT Processing changes file: net-snmp_5.7.3+dfsg-1.7+deb9u1_s390x.changes ACCEPT
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> unarchive 896893
Bug #896893 {Done: James Cowgill } [release.debian.org]
transition: ffmpeg
Unarchived Bug 896893
> forcemerge 888357 910795
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Bug #910795 [src:opal] libopal3.10.10: package uninstallable
896893 was blocked by: 888385 888345 888353 888360 888343 888344 888384 888356
896823 888335 888357 888386 888326 888352 888338 888328 888332 888381 888325
904104 904267 888330 888376 888375 888370 888380 888374 888329 888336 888383
888378 888372 888371 888346 888367 888349 888350 888364 888389 888377 896824
896825 888373 888331 888347 888382 888333 888359 888362 888337 888388 888365
888363 888358 888340 888366
896893 was not blocking any bugs.
Added blocking bug(s) of 896893: 910795
Added indication that 910795 affects libopal3.10.10
Marked as found in versions opal/3.10.10~dfsg2-2.1.
Added tag(s) patch, buster, ftbfs, and sid.
Merged 888357 910795
> affects 888357 libopal3.10.10
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Bug #910795 [src:opal] libopal3.10.10: package uninstallable
Ignoring request to set affects of bug 888357 to the same value previously set
Ignoring request to set affects of bug 910795 to the same value previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
888357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888357
896893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896893
910795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Re: Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch
Dear Rogério, dear release team, dear backports-admins, On Sun, Sep 16, 2018 at 02:57:30PM +0200, Thierry wrote: > Package: youtube-dl > Version: 2017.05.18.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > the version of youtube-dl that is shipped with stretch does not work > anymore for the youtube website, making the package unusable for some > videos. It should be updated to a more recent version. If this is not > possible by Debian policy, stretch-backport should provide a recent > version. (it's not only youtube that's broken but also others..) For the 2nd time in 2 months today I have installed a local backport of youtube-dl on my machine (and soon will do the same at friends...) so by now I'm also pretty close to upload youtube 2018.09.10-1~bpo9+1 to stretch-backports to solve this (better) for "me" (and others) but then I really do believe this should be fixed by uploading 2018.09.10-1~deb9u1 to stable(-updates). what's your stance on this? I'm happy to prepare uploads to either if that helps. (and a proper bug if the stable updates route is chosen.) -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_armel.changes ACCEPT Processing changes file: dnsmasq_2.76-5+deb9u2_armhf.changes ACCEPT Processing changes file: dnsmasq_2.76-5+deb9u2_mips.changes ACCEPT Processing changes file: dnsmasq_2.76-5+deb9u2_ppc64el.changes ACCEPT Processing changes file: dnsmasq_2.76-5+deb9u2_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_arm64.changes ACCEPT
NEW changes in stable-new
Processing changes file: linux_4.9.130-1_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_all.changes ACCEPT Processing changes file: linux_4.9.130-1_all.changes ACCEPT Processing changes file: nagstamon_2.0.1-5+deb9u1_all.changes ACCEPT
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_amd64.changes ACCEPT Processing changes file: dnsmasq_2.76-5+deb9u2_i386.changes ACCEPT
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_mipsel.changes ACCEPT Processing changes file: linux_4.9.130-1_arm64.changes ACCEPT Processing changes file: linux_4.9.130-1_ppc64el.changes ACCEPT
NEW changes in stable-new
Processing changes file: dnsmasq_2.76-5+deb9u2_mips64el.changes ACCEPT
Bug#910549: nmu: xapian-core_1.4.7-2
On Mon, Oct 08, 2018 at 12:29:54PM +1300, Olly Betts wrote: > The new xapian-core was uploaded close to two days ago and has > now built everywhere except kfreebsd-*. It's now built everywhere. > 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. No further uploads which used the old libxapian-dev. There's been a notmuch upload using the new libxapian-dev, so notmuch no longer needs a binnmu. Here's a revised list for convenience: 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 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)' Cheers, Olly
NEW changes in stable-new
Processing changes file: linux_4.9.130-1_amd64.changes ACCEPT
Bug#901015: transition: protobuf
On 2018, ഒക്ടോബർ 12 12:36:45 PM IST, "László Böszörményi (GCS)" wrote: > Uploaded ProtoBuf with the latest gRPC to Sid. Thanks a lot for your work! I hope to upload them to stretch-backports as soon as they enter testing (I have rebuilt them for my personal repo before). -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#910549: marked as done (nmu: xapian-core_1.4.7-2)
Your message dated Sat, 13 Oct 2018 06:24:00 + with message-id and subject line Re: Bug#910549: nmu: xapian-core_1.4.7-2 has caused the Debian Bug report #910549, regarding nmu: xapian-core_1.4.7-2 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 ow...@bugs.debian.org immediately.) -- 910549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@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 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Olly Betts: > On Mon, Oct 08, 2018 at 12:29:54PM +1300, Olly Betts wrote: >> The new xapian-core was uploaded close to two days ago and has >> now built everywhere except kfreebsd-*. > > It's now built everywhere. > >> 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. > > No further uploads which used the old libxapian-dev. > > There's been a notmuch up
