mirror of
https://github.com/CyberMind-FR/secubox-deb.git
synced 2026-07-29 18:36:55 +00:00
edb3ce79b2
The discover step previously scheduled an amd64 build for every
non-arch-all package, ignoring an explicit `Architecture: arm64`
or `Architecture: amd64` in debian/control. The amd64 job then
failed with `dpkg-genbuildinfo: error: binary build with no
binary artifacts found` because dpkg produces zero binaries for
an arch-foreign declared package on the build host.
Replace the implicit "amd64-always" logic with a case on the
binary stanza's Architecture field:
all -> amd64 (the arch-all .deb deployable on any arch)
any -> amd64 + arm64 (preserve current behavior)
amd64 -> amd64 only
arm64 -> arm64 only
Local dry-run on the current 133-package catalog: 132 amd64 + 1
arm64 combos (secubox-daemon is the only arch-any package), well
under the 256-jobs-per-matrix GH Actions cap.
Read the Architecture from the BINARY stanza (after Package:) so
the Source stanza's Architecture (which Debian convention sometimes
omits) doesn't interfere — awk pattern is `/^Package:/{p=1} p && /^Architecture:/{print $2; exit}`.
Co-authored-by: CyberMind-FR <gandalf@Gk2.net>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| build-all-live-usb.yml | ||
| build-eye-remote.yml | ||
| build-image.yml | ||
| build-installer-iso.yml | ||
| build-live-usb.yml | ||
| build-multiboot.yml | ||
| build-packages.yml | ||
| build-secubox-cli.yml | ||
| dashboard-cache-check.yml | ||
| license-check.yml | ||
| publish-packages.yml | ||
| release.yml | ||
| sync-all.yml | ||