CI builds a changed recipe and needs a new package; 4.0.4-1 is already
published. The pinned upstream source has no guard files, so 4.0.4-2 has the
same contents.
Moving omarchy-hw-platform from omarchy to omarchy-settings loses the file
when the dev pair installs in separate transactions, since omarchy-dev does
not pin omarchy-settings-dev's version. Settings now installs a copy beside
the guard script and omarchy keeps its detector, so no file changes owner.
The settings package's platform guard runs omarchy-hw-platform before the
omarchy runtime is installed. omarchy leaves the detector out of its bin/
loop and settings ships it, with the /usr/share/omarchy/bin link the Apple
predicate and the CLI router use, whenever the source has it.
The guard hook and the script it runs install together from omarchy-settings,
so they are resident before the runtime and hardware packages. Conditional, so
builds from sources without them are unchanged.
On aarch64 the Limine hooks and the mkinitcpio wrapper run through
limine-apple-gate. Only an Apple Silicon Mac (device tree "apple,")
behaves differently: Limine's kernel and removal hooks wait until
Omarchy activates Limine (/var/lib/omarchy/limine.enabled and
/etc/default/limine), mkinitcpio's own kernel hook keeps /boot current
before and after activation, Limine's EFI deploy hook is left to
omarchy-mac-boot, and the wrapper is plain mkinitcpio. Skipped hooks
drain the socket pacman streams targets over.
x86_64 packages exactly what 1.39.0-1 did; generic aarch64 and
Snapdragon keep upstream behaviour.
Packages only packages/omarchy-mac from omacom/omarchy-mac at an exact
quattro-upstream commit, restricted to aarch64 and the edge channel.
Ported from the omarchy-mac/omarchy-pkgs-aarch64 recipe.
Co-authored-by: Scott Jones <scottajones@gmail.com>
A replaces rule applies to any root with the omarchy repo, so a generic
aarch64 system carrying wireguard-arch would be offered this Apple-only
kernel on -Syu. ALARM's linux-aarch64 carries no replaces either.
Ported from the asahi-quattro lane. Both are pinned by hand like
linux-aurora and restricted to aarch64 and the edge channel from their
first merge, since merging publishes. pkgrel sits one above the fork
lanes' builds so the same filename never carries two sets of bytes.
The kernel provided linux=, so on any aarch64 root with the omarchy repo
listed before core, a dependency on linux resolved to this Apple-only kernel
instead of ALARM's linux-aarch64. linux-asahi and WIREGUARD-MODULE stay.
Channel membership narrows to edge until M1 and M2 cold-boot qualification;
promotion widens it again. pkgrel moves to 10 because 7.1.12.aurora2-9 is
already published and a filename is immutable.
qemu-binfmt-conf.sh groups arm with aarch64 and skipped it; Apple Silicon has
no AArch32 execution, so --ignore-family is needed for ARM32 programs. The
bin/sync-upstream extension, its tests and the Tests workflow edit are
reverted; QEMU updates become reviewed pins.
Chromium sandboxes through unprivileged user namespaces on Arch-family
kernels, so the setuid-root helper is unnecessary. The watcher tests now run
from check() as checksummed package sources, leaving tests/ and the shared
Tests workflow untouched.
Aurora Silicon's fork of the Asahi kernel (DisplayPort alt-mode and USB4
for external displays, VRR, ISP and AOP drivers) as an aarch64-only split
package, linux-aurora and linux-aurora-headers, pinned to an immutable
commit that was cold-boot qualified on a MacBook Pro 14" M1 Pro and 16"
M2 Max. It provides and conflicts with linux-asahi so Macs move over in
one explicit transaction, and pkgrel 9 orders it after the last build the
maralcbr fork published, so already-installed Macs upgrade on -Syu.
Metadata: skip_build like the x86 kernels (built only by its own PR),
release_ring fast with channels edge and rc, so one merge publishes the
same artifact to edge/aarch64 and rc/aarch64 and stable keeps asahi-alarm's
linux-asahi. No x86 job is emitted and no shared tooling changes.
Update both package recipes and source checksums to OWE 0.2.6. This release includes the transition-image timeout and output-selection fixes. Package builds pass on x86_64 and aarch64.