Repository navigation
Carry Snapper and first-run service fixes in ARM package builds - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Carry omacom/omarchy-pkgs#341 in the ARM package build pipeline, without waiting for the upstream recipes to merge.
patches/omarchy-first-run-packages.patch(Snapper dependency on ARM; conditional keyboard-backlight user service installation in stable/dev settings recipes).Verification
bash scripts/self-test.sh: all 51 checks pass, including actual package-archive validation for absent Snapper, forbidden Limine dependencies, missing/stale/matching keyboard service, and older release sources.6d27290193109c07b0134360d382e64790ae5dda.b81d678: all eight stable/dev × ARM/x86 × current Mac source/actual stable pin combinations pass using the desktop companion regression test.a190c0e. Its stable recipe stages successfully across ARM/x86 and current/pinned source (four cases), including matching keyboard service where applicable.plocate-updatedb.service.d/10-omarchy.conf. Reproduced without our patch; this is an independent upstream dev/old-source compatibility limitation. This repository's release workflow builds the stable pair, not the dev recipes.Scope and follow-up
No release assets were published, version tags changed, or PRs merged. Existing release detection/version ordering remains unchanged; publishing these fixes still needs an appropriately versioned Mac release.
The upstream PR remains open. omacom/omarchy-mac#372 still checks out upstream recipes directly: this ARM-repository port does not automatically resolve that desktop CI dependency. CI must consume the patched recipes or wait for the upstream merge; the test should not be disabled.