feat(arch-repo): publish aarch64 packages alongside x86_64 (#6334)#6358
Merged
Conversation
The pacman repository published only x86_64. Extend it to aarch64 (Arch Linux ARM) for librefang-bin and librefang-docker. librefang-desktop-bin stays x86_64-only because upstream ships no ARM Linux desktop bundle (the arm64 release assets are Windows/macOS only).
publish-arch-repo.sh now loops over ARCHES (default "x86_64 aarch64"), publishing one signed pacman repo per arch under arch/<arch>/. Clients select it automatically via pacman's $arch in the existing Server line, so the install docs are unchanged.
These packages repackage prebuilt release binaries (no compile), so aarch64 is built on the x86_64 runner: librefang-bin repoints its source tarball to the aarch64-unknown-linux-gnu asset, sets arch=('aarch64') and CARCH via ~/.makepkg.conf (the arch field is metadata only), and disables !strip since the host strip cannot process foreign binaries (the release tarball is already stripped upstream). librefang-docker is arch=any and lands in every arch path.
No change to action.yml / release.yml / secrets — the multi-arch loop is internal to the script.
Verified locally (amd64 container): the aarch64 librefang-bin package builds, reports Architecture: aarch64, and file confirms the bundled binary is ARM aarch64 ELF.
github-actions
Bot
added
area/docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Extends the project-maintained pacman repository (#6352) to aarch64 (Arch Linux ARM).
It was x86_64-only. Now
librefang-binandlibrefang-dockerare also published for aarch64 underarch/aarch64/.librefang-desktop-binstays x86_64-only because upstream ships no ARM Linux desktop bundle (the arm64 release assets are Windows/macOS only).How
publish-arch-repo.shloops overARCHES(defaultx86_64 aarch64), publishing one signed pacman repo per arch underarch/<arch>/. Clients pick the right one automatically through pacman's$archin the existingServer = …/arch/$archline — no install-doc change.These packages repackage prebuilt release binaries (no compile), so aarch64 builds on the x86_64 runner:
librefang-bin: repoint the source tarball to theaarch64-unknown-linux-gnuasset, setarch=('aarch64')+CARCH(via~/.makepkg.conf), and!strip— the host strip can't process foreign binaries, and the release tarball is already stripped upstream.librefang-docker:arch=any, lands in every arch path.No change to
action.yml/release.yml/ secrets — the multi-arch loop is entirely inside the script.Verification
Local amd64 container (
fileis the decisive evidence that we shipped a real ARM package, not a mislabeled x86_64 one):updpkgsumspullslibrefang-aarch64-unknown-linux-gnu.tar.gz, sha passeslibrefang-bin-…-aarch64.pkg.tar.zst;pacman -Qip→Architecture: aarch64fileon the bundled/usr/bin/librefang→ELF 64-bit LSB pie executable, ARM aarch64 … strippedbash -nclean on the rewritten scriptThe x86_64 path is unchanged from the merged #6352 (already verified end-to-end: real
pacman -S librefang-bininstall + signature check on a live Arch container). The first CI release confirms the aarch64 path on the native amd64 runner.Refs #6334