[Debian-med-packaging] Bug#1149122: emperor: FTBFS with the nocheck build profile
Santiago Vila
sanvila at debian.org
Sat Oct 3 18:11:48 BST 2026
Hi.
I know this is weird because the build log suggests that the BD to
drop its <!nocheck> would be python3-numpy , but this is actually what
my script check-nocheck told me:
==== Checking annotations for package emperor ====
Trying with all build-dependencies
Build worked
Trying without libjs-qunit
Build worked, it is ok to keep libjs-qunit <!nocheck>
Trying without python3-click
Build worked, it is ok to keep python3-click <!nocheck>
Trying without python3-notebook
Build worked, it is ok to keep python3-notebook <!nocheck>
Trying without python3-numpy
Build worked, it is ok to keep python3-numpy <!nocheck>
Trying without python3-pandas
Build worked, it is ok to keep python3-pandas <!nocheck>
Trying without python3-pytest
Build worked, it is ok to keep python3-pytest <!nocheck>
Trying without python3-skbio
Build did NOT work, python3-skbio should not have <!nocheck>
==== build-dependencies that should drop their <!nocheck> annotation ====
python3-skbio
So that's what I did.
(There may be some other solution, but not in the form of dropping
nocheck annotations).
Thanks.
More information about the Debian-med-packaging
mailing list