Testing removal summary 2016-09-09 (Friday)
The following source package(s) have been removed from testing:
REMOVED: cnrun 1.1.14-1.1
Package not in unstable
REMOVED: darkradiant 2.0.2-2
<https://release.debian.org/britney/hints/auto-removals>
Bug #833121: darkradiant: seffaults when python scripting enabled
REMOVED: debian-edu-archive-keyring 2014.10.14
Package not in unstable
REMOVED: gpointing-device-settings 1.6.0~git20150314.de7fe9e7-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #833919: Crashes with "stack smashing detected" whenevery I try to apply changes
REMOVED: license-reconcile 0.11
<https://release.debian.org/britney/hints/auto-removals>
Bug #832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255
REMOVED: linux-tools 4.4.6-1
Package not in unstable
The following package(s) appear to have valid removal hints,
but are still in testing for some reason:
HINTED FOR REMOVAL: libvsqlitepp 0.3.13-3.1
<https://release.debian.org/britney/hints/auto-removals>
Bug #809119: libvsqlitepp: FTBFS when built with dpkg-buildpackage -A (invalid package/library name)
HINTED FOR REMOVAL: python-aiohttp 0.22.4-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #830567: python-aiohttp: accesses the internet during build
HINTED FOR REMOVAL: zope2.13 2.13.22-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #806127: zope2.13: FTBFS when built with dpkg-buildpackage -A (No such file or directory)
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: