Source: debci Severity: normal debci appears to hang, i.e. stops scheduling tests for testing, after a binary package is removed from a source package. I think this bug is triggered if the package removed was the last binary independent package.
The problem affects the transition of mshr into testing. mshr 2018.1.0+dfsg1-2 passed tests in both testing and unstable. But that's on amd64. mshr 2018.1.0+dfsg1-2 failed to build on i386 and other 32 bit arches. To help with the 32 bit build problems, I dropped the arch-independent package mshr-demos, moving demos to python3-mshr. Later versions of mshr continue to pass debci tests on unstable. But tests on testing remain frozen at 2018.1.0+dfsg1-2. PTS reports "arch:all not built yet, autopkgtest delayed". So debci is waiting for a package (mshr-demos) which no longer exists. I've filed bug#907513 to expunge all trace of mshr-demos. But nevertheless, I think it is a bug that debci hangs on a missing package like this. Drew -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
