Testing removal summary 2018-05-22 (Tuesday)
The following source package(s) have been removed from testing:
REMOVED: apt-offline 1.8.1
<https://release.debian.org/britney/hints/auto-removals>
Bug #871656: apt-offline: Does not validate Packages or .deb files in bundle
REMOVED: bcfg2 1.4.0~pre2+git141-g6d40dace6358-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #896618: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
REMOVED: bottleneck 1.2.0-6
<https://release.debian.org/britney/hints/auto-removals>
Bug #896619: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
REMOVED: faustworks 0.5~repack0-5
<https://release.debian.org/britney/hints/auto-removals>
Bug #896473: faustworks FTBFS with Qt 5.10
REMOVED: ganeti 2.16.0~rc2-3
<https://release.debian.org/britney/hints/auto-removals>
Bug #896496: ganeti FTBFS with sphinx 1.7.2
REMOVED: ido 0.3.4-1.1
<https://release.debian.org/britney/hints/auto-removals>
Bug #895039: ido: deprecated in Debian, switch over to ayatana-ido
REMOVED: kazam 1.4.5-2
<https://release.debian.org/britney/hints/auto-removals>
Bug #896550: kazam: Binding '<Super><Ctrl>R' failed!
REMOVED: mate-indicator-applet 1.20.0-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #895039: ido: deprecated in Debian, switch over to ayatana-ido
# in ido
REMOVED: nfstrace 0.4.3.1-3
<https://release.debian.org/britney/hints/auto-removals>
Bug #896467: nfstrace FTBFS with TeX Live 2018
REMOVED: pyevolve 0.6~rc1+svn398+dfsg-9
<https://release.debian.org/britney/hints/auto-removals>
Bug #896625: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
REMOVED: python-expyriment 0.7.0+git34-g55a4e7e-3.3
<https://release.debian.org/britney/hints/auto-removals>
Bug #896632: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
REMOVED: rss2irc 1.1-2
<https://release.debian.org/britney/hints/auto-removals>
Bug #896505: FTBFS: needs to be patched for newer feed API
REMOVED: ruby-api-pagination 4.2.0-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #895107: ruby-kaminari: FTBFS: InvalidSpecificationException
# in ruby-kaminari
REMOVED: ruby-kaminari 1.0.1-4
<https://release.debian.org/britney/hints/auto-removals>
Bug #895107: ruby-kaminari: FTBFS: InvalidSpecificationException
REMOVED: sphinx-argparse 0.1.15-3
<https://release.debian.org/britney/hints/auto-removals>
Bug #896636: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
The following package(s) appear to have valid removal hints,
but are still in testing for some reason:
HINTED FOR REMOVAL: android-framework-23 6.0.1+r72-4
<https://release.debian.org/britney/hints/auto-removals>
# 853310,853311,853312,886122,886204,892170 in android-platform-system-core,android-platform-system-extras
Bug #894285: android-framework-23 FTBFS with openjdk-9
HINTED FOR REMOVAL: apex 1.6.10
<https://release.debian.org/britney/hints/auto-removals>
Bug #865585: apex FTBFS: No rule to make target 'debian-nslu2-armel_config'. Stop.
HINTED FOR REMOVAL: htsjdk 2.8.1+dfsg-2
<https://release.debian.org/britney/hints/auto-removals>
Bug #894289: htsjdk FTBFS with openjdk-9
HINTED FOR REMOVAL: nis 3.17.1-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #862778: Port from libnm-glib to libnm (or GNetworkMonitor)
HINTED FOR REMOVAL: picard-tools 2.8.1+dfsg-4
<https://release.debian.org/britney/hints/auto-removals>
Bug #894289: htsjdk FTBFS with openjdk-9
# in htsjdk
The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.
Reply to: