+0
Daily
154
stars
456
forks
3
watchers
2,695
prs
144
issues
0
releases
README
Omarchy Package Repository
Recipes and tooling for the packages Omarchy ships from
https://pkgs.omarchy.org//.
- Channels: edge → rc → stable. Packages only move forward.
- Architectures: x86_64 and aarch64.
- Recipes: one directory per package in pkgbuilds//, with a
PKGBUILD and .omarchy/package.json.
Contribute a package
Everything a package PR needs is in pkgbuilds//. No secrets or
access are required. To work locally you need:
- git, bash, jq, curl and a tar that reads zstd
- Docker or Podman that your user can run, to build. With Docker, a build
calls sudo to fix the ownership of its output.
- on Arch, to check an upstream declaration: Python 3.14+, vercmp, bsdtar
Questions and problems: open an issue on this repository.
Add a new package
1. Fork the repository and branch from master.
2. Create the recipe:
bash
bin/add-package my-package --local --scaffold Starter PKGBUILD and metadata
bin/add-package my-package --source aur Or import an AUR recipe once
An imported recipe is Omarchy's from then on; there is no AUR sync.
3. Write pkgbuilds/my-package/PKGBUILD to Arch packaging standards.
- List every architecture it supports in arch=(): x86_64, aarch64,
or any. CI builds each one.
- Pin every git source with commit= or tag=. An unpinned
source is rejected; tests/pinned-sources.sh checks it locally.
- Fill the checksums: run updpkgsums (from pacman-contrib) in the
package directory. For a git source it leaves a clone of the source
there; delete it before committing.
- If upstream signs its releases, list the key's full fingerprint in
validpgpkeys=() and ship the key as
pkgbuilds/my-package/keys/pgp/.asc, the way Arch does.
Builds never ask a keyserver, so a key that is not in the file fails
the build; tests/pgp-keys-vendored.sh checks it locally. Take the
key from its owner (their site or WKD), and check that its fingerprint
matches what upstream publishes:
bash
gpg --auto-key-locate clear,nodefault,wkd --locate-external-keys [email protected]
gpg --armor --export-options export-minimal --export \
pkgbuilds/my-package/keys/pgp/.asc
- Extract a vendor archive in package() with bsdtar --no-same-owner.
pacman installs the numeric owners a package records, so every file
must be owned by root. The build fails on any other owner, or on a
group other than root, tty, ftp or games.
4. Declare where new releases come from in
pkgbuilds/my-package/.omarchy/package.json, so updates arrive without
another PR. See docs/upstream-sources.md.
json
{
"source": "local",
"upstream": { "watch": { "github": "owner/project", "pattern": "v(?P[0-9]+(?:\\.[0-9]+))" } }
}
Use this watch form for a new package. The pattern must match the whole
tag, so drop the v for a project that tags 1.2.3. A github watch
reads GitHub Releases; for a project that only pushes tags, watch the tags:
Top issues
#366intel-ipu7-camera: Panther Lake-only build breaks Lunar Lake — no camera at all, and the image is upside down10 comments · 2026-09-09#1764linux-omarchy: input lag under memory pressure on Panther Lake, from slow xe DPT pinning (drm/xe#9516)6 comments · 2026-10-28#378OPR advisory sidecar (CVE metadata, refresh without rebuild)6 comments · 2026-09-10#510linux-omarchy: CS4208 quirk in 0512-sound-fixes.patch keyed on generic Intel PCI SSID 8086:7270 breaks speakers on other Macs (iMac16,2)5 comments · 2026-09-18#479linux-omarchy / linux-omarchy-bore: backport TTM swapout fix for amdgpu hard lockups after hibernate (drm/amd#5387)5 comments · 2026-09-16#1333linux-omarchy: backport AMD DCN 3.1 compbuf wait fix for black eDP/USB-C displays after s2idle4 comments · 2026-10-20#2180linux-omarchy 7.2.8+: ~46 s USB device resume stall after S3 on ThinkPad T480s (0603 xHCI, see #1871)3 comments · 2026-11-05#1871linux-omarchy: 0603-usb-updates breaks some USB HID devices on xHCI root ports (-110); upstream fix pending3 comments · 2026-10-30