Source: pygalmesh Severity: important Tags: moreinfo,unreproducible Followup-For: Bug #933848
I'm quite confused by this bug report. pygalmesh is configured to build using pybuild not cmake, and it does build that way without cmake (whether built via 'fakeroot debian/rules binary' or 'dpkg-buildpackage'), whether cmake is installed or not. Your log snippet shows dh_auto_install -O--buildsystem=pybuild I: pybuild base:217: dh_auto_install --buildsystem=cmake So your system starts building with pybuild, but in the middle of it triggers cmake instead. That's not normal, and not expected. It doesn't behave that way for me. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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