Testing removal summary 2023-12-06 (Wednesday)
The following source package(s) have been removed from testing:
REMOVED: django-macaddress 1.5.0-3
<https://release.debian.org/britney/hints/auto-removals>
# 1054372
REMOVED: gamin 0.1.10-6
<https://release.debian.org/britney/hints/auto-removals>
# 1008205
REMOVED: gitaly 16.0.8+ds1-1
<https://release.debian.org/britney/hints/auto-removals>
# 1053799 in golang-github-libgit2-git2go
REMOVED: golang-github-libgit2-git2go 34.0.0-4
<https://release.debian.org/britney/hints/auto-removals>
# 1053799
REMOVED: usbrip 2.2.2+git20221003.5093c84-2
<https://release.debian.org/britney/hints/auto-removals>
# 1042605 in terminaltables
The following package(s) appear to have valid removal hints,
but are still in testing for some reason:
HINTED FOR REMOVAL: canu 2.0+dfsg-2
<https://release.debian.org/britney/hints/auto-removals>
# 1052347
HINTED FOR REMOVAL: mame 0.258+dfsg.1-1
<https://release.debian.org/britney/hints/auto-removals>
Bug #983507: mame FTBFS on armel and mipsel: Cannot allocate memory (armel) / ar failure (mipsel)
HINTED FOR REMOVAL: rust-env-logger-0.7 0.7.1-4
<https://release.debian.org/britney/hints/auto-removals>
# 1054156
HINTED FOR REMOVAL: rust-tracing-log 0.1.3-2
<https://release.debian.org/britney/hints/auto-removals>
# 1054156 in rust-env-logger-0.7
HINTED FOR REMOVAL: terminaltables 3.1.10-2
<https://release.debian.org/britney/hints/auto-removals>
# 1042605
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: