Cross-building for older releases on trixie broken?

[Jan Kiszka]

Hi,

for some days, I'm playing with a trixie-based kas container (currently
available via kas-isar:next from upstream), and I it seems I ran into an
issue that might be isar-related: Building e.g. qemu-arm64:bookworm with
that container fails:

| Setup apt archive
| -----------------
|
| Merged Build-Depends: debhelper-compat (= 13), build-essential:amd64,
crossbuild-essential-arm64:amd64, apt-utils:amd64, libc-dev:arm64,
libstdc++-dev:arm64
| Filtered Build-Depends: debhelper-compat (= 13),
build-essential:amd64, crossbuild-essential-arm64:amd64,
apt-utils:amd64, libc-dev:arm64, libstdc++-dev:arm64
| dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
'/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive/sbuild-build-depends-main-dummy.deb'.
| Ign:1 copy:/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive
./ InRelease
| Get:2 copy:/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive
./ Release [609 B]
| Ign:3 copy:/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive
./ Release.gpg
| Get:4 copy:/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive
./ Sources [690 B]
| Get:5 copy:/build/sshd-regen-keys-QAjoa6/resolver-ruuPrM/apt_archive
./ Packages [733 B]
| Fetched 2032 B in 0s (0 B/s)
| Reading package lists...
| Reading package lists...
|
| Install main build dependencies (apt-based resolver)
| ----------------------------------------------------
|
| Installing build dependencies
| Reading package lists...
| Building dependency tree...
| Reading state information...
| E: Unable to locate package sbuild-build-depends-main-dummy
| apt-get failed.
| E: Package installation failed
| Not removing build depends: cloned chroot in use
| Reading package lists...
| Building dependency tree...
| Reading state information...
| E: Unable to locate package sbuild-build-depends-main-dummy
| apt-get failed.
|

That was part of the sshd-regen-keys package build, but all package seem
to fail this way.

I suspect we are improperly using the host dpkg tooling here, rather
than that from the target distro (see other recent discussions we had
here)...

Jan

--
Siemens AG, Foundational Technologies
Linux Expert Center

[Uladzimir Bely]

Hello, Jan.

I took a quick look at this. It seems cross-building is broken for
trixie host only for bookworm target. Buster, bullseye and trixie
targets looks OK.

The reason is still not clear for me - some failure happens with
apt/dependencies, even before dpkg-buildpackage is called.

Will try to debug.


--
Best regards,
Uladzimir.

[Jan Kiszka]

Hmm, maybe we are lucky with the other ones, but the same issue applies
in principle.

> The reason is still not clear for me - some failure happens with
> apt/dependencies, even before dpkg-buildpackage is called.
>
> Will try to debug.
>

Thanks in advance!

[Uladzimir Bely]

Hello again.

Got some time to debug it a bit more, but with no success.

So, the picture is still the same:

- Cross building trixie/bookworm (host/target) fails.
- It fails on any target architecture
- Non-ross building trixie/bookworm (host/target) is OK
- Cross building trixie/buster, trixie/bullseye, trixie/trixie is OK.

For me it looks like sbuild issue. But the reason remains unclear. ALl
build depependencies sbuild lists are already in sbuild chroot, but if
fails to generate dummy package...

Probably, it could be useful to try trixie/bookworm cross-building
outside of isar to get clear understanding if sbuild itself is in blame
or the way we use it is incorrect.


--
Best regards,
Uladzimir.