Hi, Quoting Santiago Vila (2024-12-16 22:21:44) > El 16/12/24 a las 20:41, Santiago Vila escribió: > > I'll try again with sbuild 0.88.1 and see what happens. > > Ok, tried again with 0.88.1 and it fails in the same way. > > If it's a bug in sbuild, it would be one that has not been reported before. > > I'm Cc:ing josch in case he can look at this and tell us what he thinks. > > (the strange thing is that the same version used to build ok in trixie > last time, so something has changed and I don't know what it could be)
eight days ago, the upload of python-markdown 3.7-2 switched it to Multi-Arch:foreign. Packages that are M-A:foreign are not supposed to satisfy dependencies annotated with :native according to dpkg. See also the second point in this section of the crossbuild guidelines: https://wiki.debian.org/CrossBuildPackagingGuidelines#Avoid_the_.27:native.27_qualifier_if_possible Luckily it seems that gobject-introspection is the only source package which annotated python3-markdown with :native so there does not seem to be more fallout from this change in python-markdown 3.7-2. In an earlier mail to #1090228, Simon McVittie already identified what I wrote above as the cause for this FTBFS. I'm just echoing it here in a bit more verbose way. > I see there is a changelog entry in sbuild which may be related to this: > > [ Johannes Schauer Marin Rodrigues ] > * lib/Sbuild/ResolverBase.pm: disable the sbuild-cross-resolver without > apt-utils in the chroot This is completely unrelated to this problem because the sbuild-cross-resolver is only ever going to get used when cross-building. > the strange thing is that the same version used to build ok in trixie > last time, so something has changed and I don't know what it could be What changed is python-markdown as Simon noticed already. And I agree with Simon that the correct fix is to change the Build-Depends on python-markdown:native and remove the :native qualifier. Thanks! cheers, josch
signature.asc
Description: signature
