Package: ftp.debian.org Severity: normal Hi,
The source package txtorcon no longer builds the binary package python-txtorcon. The binary package is still in archive and was not auto-decrufted. Removing the package breakds two other packages: |bigeasy@coccia:~$ dak rm -Rnb python-txtorcon |Will remove the following packages from unstable: | |python-txtorcon | 18.0.2-1 | all | |Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintain...@lists.alioth.debian.org> | |------------------- Reason ------------------- | |---------------------------------------------- | |Checking reverse dependencies... |# Broken Depends: |ooniprobe/contrib: ooniprobe | |# Broken Build-Depends: |foolscap: python-txtorcon |ooniprobe/contrib: python-txtorcon (>= 0.14.2) | |Dependency problem found. Both packages have a RC bug open: - #909866 ooniprobe: (Build-) Depends on vanished package python-txtorcon - #911271 foolscap: (Build) Depends on non existing python-txtorcon python-txtorcon itself can't be installed in unstable anymore (#905253) so I doubt it makes sense to wait until the two packages get fixed. It seems that BTS things that #905253 is still open because the package is in archive and piuparts tests with the old binary and fails. I think this is the reason why the package can't migrate to testing. I don't understand however why the package does not pop up in the cruft report. Sebastian
