On Mon, 16 Dec 2024 at 17:50:25 +0000, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build
The build log from reproducible-builds.org suggests that the problem is that apt and dpkg disagree on whether the build-dependencies are met, most likely triggered by python3-markdown having been changed from Multi-Arch: no to Multi-Arch: foreign. See also #1023438. On reproducible-builds.org, pbuilder-satisfydepends builds and installs a package that depends on python3-markdown:native: > -> Creating pbuilder-satisfydepends-dummy package > Package: pbuilder-satisfydepends-dummy ... > Depends: ..., python3-markdown:native, ... and apt is happy to install it: > Get: 174 http://deb.debian.org/debian trixie/main amd64 python3-markdown all > 3.7-2 [85.2 kB] but then dpkg considers the build-dependencies to be unsatisfied: > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-markdown:native Similarly when using sbuild, sbuild installs python3-markdown, but then dpkg-checkbuilddeps fails (same error message). We can probably work around this by swapping the build-dependency to python3-markdown, without the :native qualifier. > -------------------------------------------------------------------------------- > [...] This does not seem like a particularly useful build log: I think whatever automation you're using to report these bugs is deleting too much of it in this case. smcv
