Hello again,
Martin Pitt [2026-05-29 5:44 +0200]:
> Hmm, c-machines is Architecture: all. Conceptually, building on just the
> supported architectures is right, but it'd have to become arch: any then and
> that's difficult because reasons (esbuild yadayada).
>
> I'll make the dependency architecture specific as a quick fix to unblock
> migration.
That doesn't actually work:
Depends: libvirt-daemon-system [amd64 arm64 loong64 mips64el ppc64 ppc64el
riscv64 s390x sparc64],
fails with
dpkg-gencontrol: error: the Depends field contains an arch-specific
dependency but the package 'cockpit-machines' is architecture all
I initially thought apt/dpkg would resolve these at runtime, but apparently
they are resolved statically during package build. So I'm now between a rock
(can only build an arch: all package) and a hard place (can't express arch
specific dependencies).
AFAICS there are only these options:
1. Make c-machines Arch: specific and restrict the architectures further to
the ones nodejs supports
2. Lower libvirt Depends: to Recommends: to "smuggle" them through dependency
checks
I'll go with 1, and hope the nodejs build works on the other arches.
Martin
