Source: profanity Version: 0.10.0-1 Severity: normal Tags: upstream User: debian-cr...@lists.debian.org Usertags: cross-satisfiability Control: forwarded -1 https://github.com/profanity-im/profanity/issues/851
This is an upstream issue, but am filing it in the Debian BTS to avoid duplicated effort. The cross build dependencies fail to satisfy due to Build-Depping on python3-dev, which is too broad a metapackage and tries pulling in the host architecture's Python interpreter. For its purposes, Profanity might need only to depend on libpython3- dev. Unfortunately, Profanity only checks for the unprefixed python3- config tool and doesn't try pkg-config, which means it will find the build system's Python library instead of the host. When the upstream build system is more robust, switching the build-dep to libpython3-dev should be tried. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (2, 'unstable'), (1, 'testing-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
signature.asc
Description: This is a digitally signed message part