RE: Building Debian bookworm images for arm64 currently broken

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

> -----Original Message-----
> From: Bezdeka, Florian (T CED SES-DE) <florian.bezdeka@siemens.com>
> Sent: Thursday, September 29, 2022 7:30 PM
> To: isar-users@googlegroups.com
> Cc: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>; Moessbauer, Felix (T CED
> SES-DE) <felix.moessbauer@siemens.com>
> Subject: Building Debian bookworm images for arm64 currently broken
> 
> Hi all,
> 
> the upstream Debian testing/bookworm repositories are currently in a state
> where different package versions are shipped for different architectures. This
> shouldn't be something new or surprising, but as libc-bin is affected it might
> simply ease the disclosure of a Isar bug because a lot of other packages depend
> on libc.
> 
> libc-bin for x86 was updated to 2.35 recently while arm64 is still on 2.34.
> 
> When trying to build a Debian bookworm based image for arm64 I get the
> attached error.
> 
> Are we kind of mixing information from the build-schroot into the target-
> schroot? Would be very kind if someone with sbuild knowledge would look into
> that.

Hi Florian,

This looks indeed a bit strange but this is how sbuild generates cross-build dependencies.
The libc6-dev:arm64 is one of the default build dependencies.

If you look closely, you also see that in the following line:
Merged Build-Depends: debhelper (>= 10), build-essential:amd64, fakeroot:amd64, crossbuild-essential-arm64:amd64, libc-dev:arm64, libstdc++-dev:arm64

Actually I don't know why sbuild generates the default deps like that, but there is probably a reason to it.

Apart from that, the "customizations" is built as an arch=arm64 package, but it perfectly qualifies as an arch=all package.
That's more in line with Debian policies.
To change this, simply add `DPKG_ARCH = "all"` to the recipe.

Best regards,
Felix

> 
> Best regards,
> Florian