Skip to content

Take the Apple Silicon packages from Omarchy instead of Asahi ALARM - #19261

Draft
maralcbr wants to merge 4 commits into
quattrofrom
omacom/drop-asahi-alarm-repo
Draft

maralcbr wants to merge 4 commits into
quattrofrom
omacom/drop-asahi-alarm-repo

Conversation

@maralcbr

@maralcbr maralcbr commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

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}.conf lose [asahi-alarm]. The order is now [omarchy] [core] [extra] [alarm], and pacman-templates-test.sh asserts it. These templates are what new installs get and what a channel change writes.
  • install/omarchy-aarch64-apple.packages names aurora-bless. asahi-bless only resolved to it through a provide, and picked asahi-alarm's asahi-bless while that repository was configured.
  • update-keyring-test.sh uses example-keyring as fixture data in place of asahi-alarm-keyring. docs/file-layout.md no longer says omarchy-mac names it.

The manual/*/49-omarchy-on.md mention 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-alarm helper does four things:

  • removes [asahi-alarm] from the live pacman.conf
  • upgrades
  • removes asahi-alarm-keyring
  • deletes key 12CE6799A94A3F1B5DDFFE88F576553597FB8FEB

A migration would have to wait while a channel lacks the replacement packages. A waiting migration blocks every later migration and skips omarchy-update-boot after 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:

  1. The end state is zero asahi-alarm dependency, with no fallback repository.
  2. Asahi-branded tools are renamed aurora-* with provides/conflicts/replaces. Generic projects keep their names.
  3. Everything is built from source on Omarchy's builders, and asahi-alarm binaries are never mirrored.
  4. Same-name packages use asahi-alarm's pkgver with a higher pkgrel, so installed Macs switch cleanly.
  5. Removing the repository comes last, in its own PR set (this one and the PRs below).

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:

  • the full import set: aurora-scripts, aurora-fwextract, lzfse, speakersafetyd, bankstown, triforce-lv2, widevine, muvm and fex-emu
  • the keyring-free omarchy-mac 0.2.7 from omarchy-mac-pkgs#155
  • the keyring-free omarchy-mac-boot, re-pinned in omarchy-pkgs#2953

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/all on the current Omarchy release VM) and i18n-check pass on 04d3ee0.

Local (Arch Linux ARM aarch64 container): pacman-templates-test.sh 11/11, update-keyring-test.sh 16/16, migrate-scope 7/7 and platform-packages 11/11 pass.

Resolution with the new edge pacman.conf, which lists only [omarchy] plus Omarchy's Arch Linux ARM mirror:

== repos: omarchy core extra alarm
== imports in [omarchy] edge
  aurora-scripts    20261023-1         provides: asahi-scripts=20261023 | replaces: asahi-scripts
  aurora-fwextract  0.9.2-1            provides: asahi-fwextract=0.9.2 | replaces: asahi-fwextract
  lzfse             1.0-2
  speakersafetyd    2.0.1-2
  bankstown         1.1.0-3
  triforce-lv2      0.3.2-2
  widevine          4.10.2891.0-2      provides: chromium-widevine
  muvm              0.7.0-2
  fex-emu           2604-1             provides: FEX-Emu=2604 | replaces: FEX-Emu
  aurora-bless      0.4.4.aurora2-1    provides: asahi-bless=0.4.4.aurora2
== resolve each name in install/omarchy-aarch64-apple.packages
  FAIL omarchy-mac: unable to satisfy dependency 'asahi-alarm-keyring' required by omarchy-mac
  FAIL omarchy-mac-boot: unable to satisfy dependency 'asahi-alarm-keyring' required by omarchy-mac-boot
  OK   aurora-bless -> omarchy/aurora-bless 0.4.4.aurora2-1
  OK   avd-fw -> omarchy/avd-fw 0.1-1
  OK   libva-v4l2_request-avd -> omarchy/libva-v4l2_request-avd 1.3.r11.r169.gc653eaa-1
  OK   widevine -> omarchy/widevine 4.10.2891.0-2
  OK   wf-recorder -> extra/wf-recorder 0.6.0-2
== whole Apple list, assuming asahi-alarm-keyring (what omarchy-pkgs#2953 removes)
  OK: 347 packages: 25 core, 293 extra, 29 omarchy
== full default set (omarchy-pkg-defaults aarch64-apple), assuming asahi-alarm-keyring
  OK: 178 names -> 744 packages: 54 core, 618 extra, 72 omarchy
== install the Apple list (asahi-alarm-keyring assumed): pacman exit 0
  installed omarchy-mac 0.2.3-2, omarchy-mac-boot 20261104-2, aurora-bless, widevine 4.10.2891.0-2,
  aurora-scripts, speakersafetyd 2.0.1-2, bankstown 1.1.0-3, triforce-lv2 0.3.2-2; no foreign packages

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-arch and mesa-fex-emu-overlay-*, which asahi-alarm's steam depends on, exist only in asahi-alarm.
  • aurora-audio, alsa-ucm-conf-aurora and aurora-bless provide the asahi names but don't replaces= them. The image ships the aurora builds, so image-installed Macs are unaffected.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant