Package: sbuild
Version: 0.91.1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

We recently updated our KAS tool from Debian bookworm to Debian trixie and 
faced a regeression when building our Debian Linux images with isar [1]. 
See also the isar mailling list [2].

We tracked the issue down to this sbuild change [3].

I'm not sure if I understand the implications here correctly, but
doesn't that mean that the installation of packages in the DEB_HOST_ARCH
doesn't work anymore?

When running sbuild in a cross-build scenario (chroot in DEB_BUILD_ARCH
compiling a package for DEB_HOST_ARCH) the package build fails as soon
as the apt resolver tries to install a Build-Dependency from the foreign 
architecture (e.g. foo:arm64).

A error log as example can be found on the isar mailing list [2].

In the example the following dependencies are generated from the 
resolver during sbuild (chroot is amd64):

```
| Merged Build-Depends: debhelper-compat (= 13), build-essential:amd64,
crossbuild-essential-arm64:amd64, apt-utils:amd64, libc-dev:arm64,
libstdc++-dev:arm64
```

[1] https://github.com/ilbers/isar
[2] https://groups.google.com/g/isar-users/c/H1AuILdBBMI
[3] https://salsa.debian.org/debian/sbuild/-/merge_requests/69/diffs

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.14.0-33-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, 
TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages sbuild depends on:
ii  iproute2        6.17.0-1
ii  libsbuild-perl  0.91.1
ii  perl            5.40.1-6
ii  uidmap          1:4.18.0-2

Versions of packages sbuild recommends:
ii  mmdebstrap      1.5.7-3
ii  sbuild-schroot  0.91.1

Versions of packages sbuild suggests:
pn  autopkgtest  <none>
pn  piuparts     <none>

-- no debconf information

Reply via email to