Moves the pin from f7ea7ecc to the head of quattro-upstream, which adds
#552's reset-prepare, reset-verify, reset-commit and reset-rollback
entrypoints, #553's luks-slots entrypoint and recovery key handling,
#556's encrypt unit output to kmsg at notice, and #560's snapshot restore
check with its limine-snapper-sync pre and post hooks. The pin's UTC date is
still 20260925, so pkgrel goes to 4. #544 is not in it, so the Plymouth
fragment still ships and no HOOKS baseline dependency applies.
Moves the pin from the boot-set integration commit to quattro-upstream,
which now has #541 with its review fixes (first boot hands off only for a
failed step, and the retry waits for NetworkManager), #543's update-verify
entrypoint, #545's provision entrypoints and #549's keyslot-only LUKS check.
#544 is not in it, so the Plymouth fragment still ships and no HOOKS baseline
dependency applies.
A pin with omacom/omarchy-mac#544 needs the settings HOOKS baseline (#542)
published first; a pin with #543's update-verify entrypoint must publish
before any runtime carrying #543. pkgrel 3 so this rebuild does not reuse the
published 20260925-2 filename.
From omacom/omarchy-mac#544 the Apple drop-ins no longer add Plymouth
themselves and build on omarchy-settings' 00-omarchy-hooks.conf (#536). A
settings version cannot express that (quattro candidates sort below stock
releases and omarchy pins its settings exactly), so a build whose payload has
no 93-omarchy-mac-plymouth.conf depends on the name
omarchy-mkinitcpio-hooks-baseline, which settings packages that ship the
baseline must provide.
Pin a09ee0ca, the head of omacom/omarchy-mac integ/boot-set-1 (#547): quattro-upstream with #527, #540, #545 and #541 merged. The package then carries the Apple provisioning entrypoints from #545 and can publish before those PRs merge.
groups=('omarchy-platform-apple-silicon') is the platform tag the pacman
platform guard reads (omacom/omarchy-mac#539); the package is not published
yet, so it carries the tag from its first build. The pin moves to 3a58abb5,
omacom/omarchy-mac#541 with #527's current head merged in.
DRM.cpp needs more than 8 MiB of compiler stack. GCC raises its own limit
natively, but the aarch64 builder runs under QEMU user-mode emulation, which
fixes the guest stack at exec and ignores setrlimit, so cc1plus segfaulted.
Unpatched 0.15.1 fails the same way. QEMU_STACK_SIZE sizes it at exec; native
builds ignore it and the object code is identical.
Moves the pin to 602266c8, where first boot of a fresh image refuses to finish
without the build manifest that defers its hardware setup. asahi-scripts is
the one Apple-only dependency; the README no longer calls them all generic.
The Apple Silicon boot package (Mac initramfs, in-place encryption, first
boot and the Limine activation gate) now builds from packages/omarchy-mac/boot
in omacom/omarchy-mac at a pinned commit: the recipe runs the source's tests
and install staging, and keeps only metadata, backup= and the pacman
scriptlet from the fork recipe. aarch64 and edge only; 20260925-1 upgrades
the fork's 20260921-10. It needs the Apple-gated limine-mkinitcpio-hook
1.39.0-2.
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.
PR builds link against published edge, so a Hyprland bump in the same merge
cannot see the carry, and as a fast-ring package it would reach every aarch64
channel. The rebuild detection fix that bumps it once the carry publishes
moves to its own PR, so this change only adds the aquamarine carry.
Carry Arch's aquamarine 0.15.1-1 with one patch that re-reads a connector's
possible CRTCs on rescan, so a Type-C port the Apple DCP fabric reroutes to
another pipeline gets a CRTC without restarting the compositor. aarch64 and
edge only; pkgrel 1.1 sits above Arch Linux ARM's 0.15.1-1.
Bump Hyprland for aquamarine 0.15.1 and make rebuild detection see aarch64.
sync-rebuilds followed PUBLISHED_ARCHES (x86_64 by default), so the scheduled
run skipped every aarch64-only package, and it read aarch64 triggers from Arch
Linux ARM even when this repository carries them. It now follows the
architectures a merge builds, and reads a carried trigger from its recipe once
edge publishes that version.
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.
Marcelo Alcantara