Repository navigation
Conversation
…c packages The migration engine leaves omarchy-mac-boot (omacom/omarchy-mac-pkgs drops it): one self-contained script built from migrate/src, journaled and resumable, that moves a quattro, mx-mac or test-image Mac onto its channel's official packages (the omarchy-dev pair on edge) and the core Apple Silicon pacman configuration, and defers while that channel has no Mac release.
A migration marks the Mac; the next omarchy update runs omarchy-mac-migrate before any fork step and stops there for the reboot, or updates the Mac as before while its channel has no Mac release. The README gives testers the one-line command.
The boundary is recorded right before the switch's first write, so a reset or a refusal before it still defers. A second run never touches the state of the run holding the lock. Preflight trusts no retired key, refuses NoExtract or NoUpgrade patterns and IgnorePkg globs that hold back what the move installs, and checks a busybox-encrypted Mac keeps its unlock under the new drop-ins. Fork leftovers the Mac packages no longer retire are retired here. The update hook stops the fork update only after a move.
…tion Preflight runs only regular files from the verified omarchy-mac-boot, never a link, and refuses a boot package without them. Its HOOKS preview drops the drop-ins of the packages the transaction replaces. A user setup that succeeds on a retry no longer releases the unit while the migration is still under way, and a migration past its switch resumes whatever a detector says.
pacman -Qlq of a package that is not installed fails, which under pipefail made the preview fail and an encrypted legacy Mac defer for good. The fixture pacman now fails the same way. The boot unit also resumes a migration past its switch whatever a detector says.
It runs as root in an empty environment and across the move to another runtime, so it cannot depend on the runtime's helpers.
|
Preflight-only report from a second legacy Mac: MacBook Pro 16" M1 Max (j316c), quattro guided install, encrypted, GRUB, ESP at This Mac also has
Skipping those the way Battery)
[[ -r $supply/scope && $(<"$supply/scope") == "Device" ]] && continue
[[ -r $supply/present && $(<"$supply/present") == 0 ]] && continue
{ capacity=$(<"$supply/capacity"); } 2>/dev/null || capacity=100 |
|
I used migrated my M1 pro to latest 4.5-RC2. Used claude to fix issue with grub migratio. Below are all the details, generated using claude Real-hardware report: legacy encrypted GRUB Mac → rc, completedMachine: MacBook Pro 16" M1 Pro (2021), 16 GB. ResultThe migration completed on real hardware. After the reboot, What I ran:
The rollback worked well. After the failed Issues found1. Workaround: comment out 2. Retiring 3. A 4. 5. Harmless but alarming: Note on rc for MacsThe 4.5.0rc2 runtime has Apple Silicon templates for edge only (
If rc isn't meant to be a Mac target yet, the rc Happy to rerun anything or collect logs from this machine. |
|
Full Result: migrated. After the reboot Two problems, both from aurora-sep:
Notes for the tests: |
|
Report: M2 Air 15" (j415), fork 4.0.3 → rc, completed; Setup: MacBook Air 15" M2 2023 (
Cause. The fork's The official
Fix on my side: then Suggestions:
Also noticed after Unrelated to the tool, but it shows in its output: this Mac's SMC RTC came up as 1970-01-12 at every boot ( |
|
Report: MacBook Pro 16" M1 Max (j316c), omarchy-mx-mac fork 4.0.4-mac.1 → rc, completed Tool at
Working afterwards: Wi-Fi, speakers, USB audio, Bluetooth, and suspend and resume (by command and by lid). External 4K works over HDMI and over USB-C (120 Hz). The charge limit held. Things I noticed:
Thanks ever so much for the tool; loving the Omarchy Mac work! I ran this with help from Claude (Claude Code), which also reviewed the PR's code beforehand and helped write this report. |
|
Another data point for the It also has Would it make sense to fold #727 and a content-based |
|
Follow-up to my comment above, from reading the code and the edge/rc packages on the same M1 Max (legacy/GRUB/encrypted, edge). I haven't run
|
|
I use Omarchy MX Mac and want an in-place migration to official Omarchy Mac. I did not attempt migration or execute the migration tool. Read-only inspection confirmed this configuration:
I read the convergence specification, MX adapter work in #571, and standalone migration proposal #690. I understand that implementation and test reports do not establish released support for this configuration. Can the maintainers clarify these points?
This is a compatibility and readiness question. I do not report a migration failure. Thank you for your guidance. |
|
Tested the development Migration tool commit: Command: The tool automatically selected the RC repository ( Exit code: Separate package metadata inspection found:
These versions suggest an ABI mismatch between the selected repository packages. The preflight's temporary repository databases were not retained, so the exact package selection could not be independently reconstructed. The preflight stopped before boot-helper execution, so compatibility with my encrypted Btrfs/LUKS2 and Limine configuration remains unverified. Are you aware of this dependency mismatch, and is a compatible package set planned for the migration preflight? Thanks! |
|
@rbadhesha On the dependency mismatch, from my M1 Max, which I migrated with Cause. On 2 Nov, Arch Linux ARM's A likely fix.
The tool's For readiness, my run is one data point: M1 Max, |
|
Follow-up from the M2 Air 13" (J413, legacy cohort, GRUB, unencrypted ext4) that ran After comparing it package by package with a fresh 4.5.0rc3 install (MBP 16" M1 Pro, installer 2.3.13), I found that the migration switches the kernel/boot core (
Everything kept working, so nothing is broken, but a migrated Mac quietly ends up on a different audio/graphics stack from a fresh one. That makes bug reports from migrated and fresh machines hard to compare. The userspace swap went cleanly by hand (the aurora packages Reboot afterwards: Mesa 26.3-devel in use, the aurora-audio DSP graph loaded, no regressions so far. I haven't swapped the boot pieces ( Related, also only on migrated machines (different cause): A mic gain lowered before the mic mapper existed stays stranded on the hidden DSP source; filed as #789. Would it make sense for the migration's target set to include these swaps, so a migrated Mac ends up matching a fresh install? |
[High impact] The PR can change the package and boot setup of eligible Apple Silicon Macs. Reject missing explicit targets before merging so the tool cannot silently install a different package set. FindingsSummaryAdds a standalone, resumable move from the Mac forks to official Omarchy packages.
|
| for candidate in "$@" "$admin_target"; do | ||
| if [[ -n $candidate && -e $candidate ]]; then | ||
| printf '%s\n' "$candidate" | ||
| return | ||
| fi | ||
| done |
There was a problem hiding this comment.
Missing targets silently fall back
find_target skips an explicit --target path when the file does not exist. For example, run --target /etc/omarchy-mac/candidate.typo instead uses the administrator's default target or the detected channel. The tool can then replace packages and the boot chain with a different set than the operator requested. Reject a missing explicit target before trying any fallback.
| if [[ -f $complete && -f $plan/target-id ]]; then | ||
| tidy_completed |
There was a problem hiding this comment.
Checking changes user settings
check calls tidy_completed before checking check_only. After a completed migration with pending user setup, this retries commands that change the user's files and settings. It can also remove the boot unit and saved tool. Skip completed-state cleanup during check so the advertised read-only command stays read-only.
|
Field report: encrypted M2 Max / Important qualification: this used a locally modified build based on #690 head The coordinated target included Aurora audio/UCM, Mesa/Vulkan, bless, U-Boot, firmware and the official libfprint provider, addressing the package-parity concern in #690 (comment). The custom Resulting versions include:
One actionable snag: the package transaction completed, but loader staging stopped with After applying the normal pending Omarchy configuration migrations and rebooting again, the official clean-environment boot check reported: No pending-reboot or rollback override was used. No failed system/user units were reported, and normal operation looks good so far. On J414, active The required core platform providers match the fresh-image builder's policy, but I have not compared the entire published image inventory or exhaustively tested every hardware path. Recovery backups and legacy boot assets are retained; final retirement has not run. |
|
Follow-up to my earlier M2 Max compatibility question and blocked preflight report: the in-place migration succeeded. Machine: MacBook Pro 14-inch (M2 Max, 2023), previously Omarchy MX Mac Qualification: I used a locally corrected build based on Results:
The migration left the older audio and graphics packages installed, consistent with the package-selection concern reported above. After migration, I separately replaced
The transaction also installed Boot-selection and firmware packages remain as installed by the migration. Recovery backups and migration records remain available. Thanks for the frozen-mirror guidance and the migration work. This follow-up records the successful outcome of my earlier preflight report. The local corrections and separate audio/graphics replacement remain important qualifications. |
|
Field report: unmodified tool, MX Mac Machine: MacBook Pro 13" M1 ( Tool: Avoiding the aquamarine ABI clash without patches:
Verify failure after the reboot: Cause: a race with Result: +1 on package parity: |
|
Field report: successful migration, legacy GRUB + LUKS, MacBook Pro 16" M1 Max (j316c) Start: fork omarchy 4.0.2-2 (edge lane), GRUB, Pre-run prep (from earlier reports in this thread):
Run notes: the prefetch took about 4.5 min. 139 locally-newer packages were kept, and a few were downgraded slightly (hyprland-preview-share-picker, localsend, yay). The transaction and boot-chain steps were clean. Two failures, both fixed by hand and resumed cleanly:
After the migration (
Suggestion: since edge-lane Macs land ahead of stable, the tool could offer the Thanks for the tool. The journal/resume design made both of these painless to recover from. |
|
Follow-up to the report above: Steam was broken after The "Orphan system packages" step of migration 1793667581 removed Fix: Steam launches again after that. Suggestion: |
|
Field report: second MacBook Pro 13" M1 ( Same starting point as @enriquebv's report (
Thanks for the tool! |
|
Field report: MacBook Air 13" M3 ( As far as I can see, this is the first J613 in this thread. Start: Omarchy fork on the Pre-run prep: the same as earlier reports, plus four refusals that came from our own customizations. They are listed in case other bring-up Macs carry similar leftovers:
One surprise during After migration, J613 on rc (aurora14):
Notes for the maintainers:
Disclosure: the preparation, the analysis and this text were made with an AI coding agent (Claude Code). The migration and all tests ran on the real J613 and were checked by me. |
|
Field report: MacBook Air 13" M2 ( As far as I can see, this is the first MX Mac in this thread that started on Start: Tool: unmodified New compared to the earlier reports:
Result: +1 on @seanfreiburg's
Unrelated to the tool: on the first I ran the tool through a small wrapper script. It:
It's tailored to this Mac, so I haven't published it, but I'm happy to share it. The wrapper and this report were written with Claude (Claude Code). All versions and messages above come from the logs of the real run. Thanks for the tool! |
|
Field report: MacBook Pro 16" M1 Max ( This is the same cohort as @seanfreiburg's j316c and @Knutsi's preflight. It's the first run in this thread from a 4.0.3rc4-2 quattro install that had followed the Start: omarchy/omarchy-settings Prep (the usual set from this thread):
First boot: Limine, the sd-encrypt passphrase prompt, and the verify unit completed
Aligning with stable (needed, as @seanfreiburg found): the migration's transaction made 37 package changes (4 downgrades) and kept everything the edge lane had made newer. So before the first
First Other changes after the update, for anyone with customised configs:
Leftovers (not harmful): the fork's Package parity: I swapped to the fresh-install stack afterwards with End state: Thanks for the tool. Its preflight-then-journal design made a legacy GRUB + LUKS move uneventful. Disclosure: the preparation, the checks and this report were done with Claude Code. Every version, message and timing above comes from the real run on this Mac. |
|
Follow-up to my j316c report above, after the aurora audio and graphics swap and a reboot:
|
|
Small correction to @arikisonfire's note: I did do the boot-piece swap on my M2 Air ( |
|
Preflight-only report from an M1 MacBook Air ( Setup: quattro install from the fork, encrypted, GRUB, ESP at
Command: Result: exit Questions:
Disclosure: Claude Code helped me prepare these checks and this report. Every version and the output above come from this Mac. |
Moving existing Macs onto Omarchy's official packages is now a standalone script, not part of any package (agreed with Ryan on 2026-10-04: the Mac packages move to omacom/omarchy-mac-pkgs without the migration engine; omacom#13362 uses them).
What it adds
omarchy-mac-migrate: a single self-contained script built frommigrate/srcbymigrate/buildand committed asbin/omarchy-mac-migrate. It is the quattro-upstream engine (Migration engine with the quattro-upstream tester transition #559, Convert legacy omarchy-mac installs to official packages and trust #564, Migrate mx-mac Macs in place (ticket 43) #571, Switch legacy Macs' boot chain to Limine, keeping their encryption #582, Migrate Macs from a verified download of omarchy-mac-boot, handing files over inside the transaction #602, Keep an administrator's migration target as it is in the Mac bootstrap #607) taken out ofomarchy-mac-bootand reworked:omarchy-devpair,omarchy-macandomarchy-mac-boot(from omarchy-mac-pkgs), the Aurora chain, and Converge omarchy-mac and omarchy-mx-mac into upstream Omarchy omarchy#13362's Apple Siliconpacman.conf. No fork package, repository, key or pin is left.IgnorePkgguard from the switch until the setup is verified;omarchy-lifecycle-dispatch(setup-boot,setup-system,setup-user,update-verify);migrations/1791080196.shmarks the Mac. The nextomarchy updateruns the tool before any fork step and stops for the reboot, or updates as before while the move defers.migrate/build --checkkeeps it current).Supersedes #603. The code of #601, #602 and #607 is the tool's source.
Tests
mac-migrate-test.sh(tester cohort, engine),mac-migrate-legacy-test.sh,mac-migrate-mx-test.shandmac-move-migration-test.sh: 104 checks. They cover kill -9 after, during and in the middle of every step, deferral before the switch and failure after it, the guard, channel detection and qualification, and leftovers.apple-test-f22c43fb7903). The target was a test-lane-signed set: the Converge omarchy-mac and omarchy-mx-mac into upstream Omarchy omarchy#13362 (69d80cc) dev pair, plusomarchy-macandomarchy-mac-bootfrom proposal/main without the engine. Everything else came from the real edge.omarchy-dev 4.0.4.r7099bundle. The rc lane deferred unchanged. On the edge lane, the fork's pair went down to the official build in one transaction, with kills during prefetch and the boot-chain rebuild resumed.encryptfromcryptdevice=, ESP at/boot,[omarchy-aarch64]lane). The ESP moved to/boot/efi, the unlock to sd-encrypt and the loader to Limine.pacman.confwas the core configuration and the migrated disk unlocked with the same password through its own boot files and reached a login. The boot unit's verification correctly refused the guest's generic kernel; completion needs a Mac.Release (owner): merge, publish
bin/omarchy-mac-migrateas releasemac-migrate-v1, and publish a quattroomarchybuild to the[omarchy-aarch64]lanes so packaged quattro installs get it (checkout installs get it fromgit pull). Nothing moves until omarchy-mac-pkgs' packages and a dev pair with omacom#13362 are on edge.