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.
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 (CI_ARCHES, shared with build-matrix), and reads a
carried trigger from its recipe once edge publishes that version; until then
its dependents wait. Published databases are verified before use and loaded
once per run.
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.
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.
The launcher called omarchy-install-hermes-cli with no arguments on every start to remove a mise-built Hermes left beside the app. Omarchy no longer builds Hermes through mise: it sets the app's runtime up before the app is opened, and the installer now only answers a named --check or --now, so the call had nothing left to reconcile and only printed usage. The launch check keeps a forbidden stand-in for that command on its PATH, so a launcher that reaches for it again fails the build.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Codex XHigh <noreply@openai.com>
Marcelo Alcantara