Re-pin omarchy-mac 0.1.0-6 and omarchy-mac-boot 20260927-1 to quattro-upstream ff7ce0d4d (edge)

[maralcbr]

Draft, HOLD: merging publishes to aarch64 edge only (both .omarchy/package.json list ["edge"]; rc and stable carry no Mac packages). The owner decides when.

What changed

• Re-pin omarchy-mac 0.1.0-5 → 0.1.0-6 and omarchy-mac-boot 20260925-4 → 20260927-1, both to omacom/omarchy-mac quattro-upstream HEAD ff7ce0d4d. That includes rc/x86_64: t3code-patched-bin-0.0.35-5 served with a checksum that does not match omarchy.db #618 (Bluetooth on first boot), Add canonical Obsidian desktop package for aarch64 #613, Add static QEMU packages for aarch64 #614, the migration fixes Carry NVIDIA DisplayPort detach fix for aarch64 #601/claude-desktop stuck at 2.2553.1; upstream Debian repo has 2.2553.13 #602/Update flea to 0.3.4 and install its ui/boot entry #607, and the boot entrypoints from Add maintainers to the vouched contributors list #543/Use matching prebuilt images for package builds and publishing #552/Carry PR build artifacts inside a tar so epoch package names survive #553/Add Task Manager for Omarchy 0.0.3 (edge preview) #579. It does not include linux-omarchy: carry ACPICA PCI bus fix for resume delays #544 (so the boot package keeps 93-omarchy-mac-plymouth.conf and needs no HOOKS baseline provider) or Add Omaridian screensaver package #603 (no packaged migration target, so activation stays held).
• Speaker safety: both packages move in one merge. omarchy-mac 0.1.0-6 enables speakersafetyd (Add ghost RT722 SoundWire fix for ASUS ExpertBook B9406 to base and BORE kernels #535), and the boot package no longer does (Package DGX Dashboard for Spark #567). omarchy-mac now also declares the runtime dependencies its README names: mkinitcpio and the protected speaker stack (asahi-audio, which pulls speakersafetyd, plus alsa-ucm-conf-asahi, rtkit and pipewire-alsa).
• omarchy-mac gets groups=('omarchy-platform-apple-silicon'), following the tagging contract in the pinned source (docs/platform-guard.md). omarchy-mac-boot already had it.
• From the first commit: check() runs boot/test/all in the full checkout. Since Add arcade: fourteen native games, including FreeSki #582/Restrict dotnet-core-bin to aarch64 and disable debug packages #598 some tests read the desktop source, so a copy-only run fails. package() still stages from the copy. The README gets publish-order bullets for Add Task Manager for Omarchy 0.0.3 (edge preview) #579 (reset first-boot markers) and Package DGX Dashboard for Spark #567 (speaker safety owner), plus re-pin step 4.

Testing

• Ran bin/build --arch aarch64 --mirror edge --package omarchy-mac omarchy-mac-boot in the CI builder image (native aarch64 container). Both packages built. check() passed: 62 ok for omarchy-mac and 277 ok for boot, 0 not ok.
• Checked .PKGINFO: both packages carry the group and the new depends. Both source-revision files are ff7ce0d4d. There is no migration-target.
• vercmp: 0.1.0-6 and 20260927-1 sort above edge's current builds and above every candidate set. That covers tools/release/candidates/* plus the draft sets 4b1081f8b, a0877ee89 and 0052582276d9 (0.1.0-5.<seq>, 20260921-10.<seq>, 20260926-1.<seq>), as well as 20260926-1.45 and 20260926-2.
• Second review: no blockers. Its note that the source declares audio depends is applied.

What publishing on edge changes

• Test-image Macs (M1 lab, M2, team preview 0052582276d9) get their packages from pkgs.omarchy.org edge, but they IgnorePkg omarchy omarchy-mac omarchy-mac-boot omarchy-settings, so omarchy update/-Syu leaves them unchanged. They would only take these packages through an explicit pacman -S/omarchy-pkg-install of those names, or by removing the pin by hand. Removing the pin is already unsafe, because it pulls stock omarchy 4.0.4.
• Image-2-era Macs had a pin without omarchy-mac-boot, so they would take boot 20260927-1 and an initramfs rebuild. None are known to be left.
• mx-mac Macs use the fork feed, and legacy omarchy-mac Macs use only [omarchy-aarch64]. Neither reads this repository. No mx-mac conversion exists until Add Omaridian screensaver package #603 and mx Add builder flags for CI and resumed builds #276 land.
• Snapdragon/DGX edge machines don't have these packages installed. The replaces= line is unchanged.
• Activation: no fresh bootstrap migration activates, because nothing packages a target. A migration an administrator starts by hand, or one that was already started and resumes, is still possible.

Verdict

This is safe to publish on edge now as an interim pin, with no known automatic recipients. It is not the qualifying pin from ticket 102 step 8: the engine still targets omarchy/omarchy-settings whatever the channel. The test pin stays, #603 stays held, and another boot re-pin (≥ 20260927-2) is needed once ticket 102 steps 3–5 merge. Edge stays unqualified until step 9. Whether to publish now or batch this with that later pin is the owner's sequencing call.

Coordination

• Tag the Mac recipes with the Apple Silicon platform group #650 bumps omarchy-mac to 0.1.0-6 at the old pin. If this lands first, rebase Tag the Mac recipes with the Apple Silicon platform group #650 until its omarchy-mac hunk disappears. If Tag the Mac recipes with the Apple Silicon platform group #650 publishes first, this PR needs pkgrel 7, because the publisher refuses different bytes under an existing filename.

[github-actions]

Publish succeeded → live

Packages: omarchy-mac (aarch64, PR artifact); omarchy-mac-boot (aarch64, PR artifact)

• edge/aarch64: omarchy-mac-0.1.0-6-aarch64, omarchy-mac-boot-20260927-1-aarch64

Some planned slots did not run because an earlier slot failed.

Commit 3a6c921 · run