Repository navigation
Conversation
Omarchy now builds every package Macs took from [asahi-alarm]: aurora-scripts and aurora-fwextract replace asahi-scripts and asahi-fwextract, and lzfse, speakersafetyd, bankstown, triforce-lv2, widevine, muvm and fex-emu are built at a higher pkgrel. The Apple Silicon templates stop listing the repository. The migration moves installed Macs over once per machine. While the repository is still configured it checks that [omarchy] carries every installed package's build, and stays pending with nothing changed when it doesn't. It then drops the section with a backup, upgrades, names anything only asahi-alarm carried, and removes asahi-alarm-keyring and its key once nothing requires the keyring.
asahi-bless only resolved to aurora-bless through its provide, and picked asahi-alarm's asahi-bless while that repository was configured.
A migration that waits for a channel's packages blocks every later migration and the boot update behind it. omarchy-mac 0.2.7 removes the repository, keyring and key itself, and it reaches a channel only together with the packages that replace asahi-alarm's.
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
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.
Apple Silicon Macs stop using the asahi-alarm repository. Every package they took from it is now built from source in omacom/omarchy-pkgs and published on edge:
Same-name packages keep asahi-alarm's pkgver with a higher pkgrel, so pacman switches them over in a normal upgrade.
What changes
default/pacman/aarch64-apple/pacman-{edge,rc,stable}.conflose[asahi-alarm]. The order is now[omarchy] [core] [extra] [alarm], andpacman-templates-test.shasserts it. These templates are what new installs get and what a channel change writes.install/omarchy-aarch64-apple.packagesnamesaurora-bless.asahi-blessonly resolved to it through a provide, and picked asahi-alarm'sasahi-blesswhile that repository was configured.update-keyring-test.shusesexample-keyringas fixture data in place ofasahi-alarm-keyring.docs/file-layout.mdno longer says omarchy-mac names it.The
manual/*/49-omarchy-on.mdmention of Asahi Alarm is about the community guide, not a dependency, so it stays.Why there's no migration here
Installed Macs are cleaned up by omarchy-mac 0.2.7 rather than by an Omarchy migration (omarchy-mac-pkgs#155). Its
omarchy-mac-drop-asahi-alarmhelper does four things:[asahi-alarm]from the livepacman.confasahi-alarm-keyring12CE6799A94A3F1B5DDFFE88F576553597FB8FEBA migration would have to wait while a channel lacks the replacement packages. A waiting migration blocks every later migration and skips
omarchy-update-bootafter the packages have already upgraded. omarchy-mac 0.2.7 reaches a channel only together with those packages, so the helper never has to wait for them.Spec decisions this implements
From the asahi import spec, decided 2026-11-17:
aurora-*with provides/conflicts/replaces. Generic projects keep their names.Release gate, per channel
This PR ships to an Apple channel (edge, rc, stable) only once that channel's
[omarchy]carries all of the following:Before that, a new install or channel change from these templates can't resolve omarchy-mac or omarchy-mac-boot (see the evidence below).
Related PRs in the set:
Evidence
CI:
test(./test/allon the current Omarchy release VM) andi18n-checkpass on 04d3ee0.Local (Arch Linux ARM aarch64 container):
pacman-templates-test.sh11/11,update-keyring-test.sh16/16,migrate-scope7/7 andplatform-packages11/11 pass.Resolution with the new edge
pacman.conf, which lists only[omarchy]plus Omarchy's Arch Linux ARM mirror:On edge today, everything resolves from Omarchy's repositories alone except omarchy-mac and omarchy-mac-boot. Their only missing dependency is
asahi-alarm-keyring, which the gate above removes. The install's scriptlet errors came from the container (no EFI partition, no systemd).Not covered here
fex-emu-rootfs-archandmesa-fex-emu-overlay-*, which asahi-alarm'ssteamdepends on, exist only in asahi-alarm.aurora-audio,alsa-ucm-conf-auroraandaurora-blessprovide the asahi names but don'treplaces=them. The image ships the aurora builds, so image-installed Macs are unaffected.