Add an official AUR package for Arch Linux / Omarchy, plus aarch64 release - #1013
Merged
Conversation
kevinaboos
force-pushed
the
arch_aur_packaging
branch
from
August 21, 2026 22:10
1c1057e to
d60e13a
Compare
kevinaboos
changed the title
kevinaboos
changed the title
kevinaboos
force-pushed
the
arch_aur_packaging
branch
from
August 22, 2026 00:04
2b2e2cd to
41b06ec
Compare
We never had an AUR entry so Arch users end up on a stale third-party robrix-bin. The pacman payload also regressed to x86_64 only somewhere along the way, pre-alpha-4 shipped both. PKGBUILD.in is the only copy of the metadata now, and render-pkgbuild.sh turns it into a real PKGBUILD for both the release build and the AUR. It checks which payloads a release actually has, so aarch64 switches on by itself once we ship one.
validate.sh was generating it and throwing it away, and a mismatch is exactly what would bounce the first AUR push. Also fixed the namcap notes, they claimed 4 warnings and the real run gives 18.
contact@robius.rs came from the old PKGBUILD.in and Cargo.toml, but the GOSIM address is the one we actually read. Maintainer stays Project Robius.
Both are derived, and the AUR repo already stores exactly what shipped. Dropping them takes the sync job and its admin PAT with them.
794 lines of setup notes for something you do once.
Not needed to build or publish anything. The error messages that pointed at the README now say what to do themselves.
kevinaboos
force-pushed
the
arch_aur_packaging
branch
from
August 22, 2026 00:11
41b06ec to
b0bfb41
Compare
Nothing was calling it. The test-build only proves the package builds, this installs it and runs ldd, so a broken depends list fails the publish instead of landing on users.
upload-artifact v4 silently excludes dotfiles, so .SRCINFO never made it from the render job to the push job and every publish would have died on the cp. Never showed up in testing because the workflow refuses to run until the AUR package exists. Also from the same review pass: guard the template's @sources@ line so a typo can't render a PKGBUILD with no sources, reuse --print-pkgver in the release notes step instead of duplicating the version munging, refuse to push over an AUR that moved while the run sat waiting for environment approval, pin PKGEXT in the test-build container like the other two, and a few validate.sh portability fixes for macOS bash and aarch64 hosts.
We didn't use robrix-bin's PKGBUILD, so crediting its author as a contributor to ours is just wrong.
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
1 participant
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.
There are some unofficial AUR packages (robrix-bin, robrix-git) but they're stuck on older releases and don't properly specify dependencies. We might as well publish an official AUR entry, so here it is.
This also includes a release action to build an aarch64 pacman packages too, not just x86_64.
There's also a new github worklow (
aur-publish.yml) that happens when the release is actually published, which makes sense because the assets pushed to a draft release have different URLs, so we have to use the published release URLs.We now depend on
libgccalone instead ofgcc-libs, which avoids pulling in another 11 lib deps that we don't need.