Testing removal summary 2018-04-30 (Monday)
The following source package(s) have been removed from testing:
REMOVED: aweather 0.8.1-1.1
<https://release.debian.org/britney/hints/auto-removals>
Bug #893023: librsl FTBFS with flex 2.6.4-6
# in librsl
REMOVED: dnssec-trigger 0.13-6
<https://release.debian.org/britney/hints/auto-removals>
Bug #862757: Should be ported from libnm-glib/libnm-util to libnm
REMOVED: jabref 3.8.2+ds-3
<https://release.debian.org/britney/hints/auto-removals>
Bug #893138: jabref: fails to build and start with openjdk-9
REMOVED: librsl 1.43-1.2
<https://release.debian.org/britney/hints/auto-removals>
Bug #893023: librsl FTBFS with flex 2.6.4-6
REMOVED: network-manager-openconnect 1.2.4-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #862884: Disable libnm-glib support
The following package(s) appear to have valid removal hints,
but are still in testing for some reason:
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: libqtdbustest 0.2+bzr42+repack1-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #879937: libqtdbustest: FTBFS: unit test fails with BadAddress DBusException
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)
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: