Repository navigation
release: 0.7.0 - #1
Merged
Merged
Conversation
Reading Omarchy PR #16100 showed what was missing here. Migrations: omarchy-mu-migrate-record@<admin>.path was only enabled by hand at install, so limited accounts could wait for good on an administrator added later. It now follows wheel (omarchy-mu-accounts sync-migration-watchers). Omarchy's first setup marks every migration done without running any, so what an account has marked when it becomes an administrator is set aside, except for the machine's first. Removing refuses system accounts, asks about the home instead of always deleting it, keeps a home holding an unfinished disk password change's note, and logs out an account with programs running before anything changes. When userdel removes the account but not its home, the rest still finishes. Adding refuses a name whose group or /home folder exists. Demoting fails when sudo -l -U still shows full sudo or the account is in docker. The last administrator is the last one who can log in, and administrator checks without a user go by the session's groups, like sudo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream's notice runs omarchy-migrate, which skips the machine-wide lock. omarchy-mu-migrate-notify now shows it itself: it waits out a running update, counts what is still pending, and a click runs omarchy-mu-migrate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/tmp/omarchy-update.log blocks the next administrator's update, and the bar's icon and the first-login notice run omarchy-update without passing through omarchy-mu-update. omarchy-mu-update-log.path moves the log to /tmp/omarchy-update.log.<owner> once nothing has it open. The package enables it, and the migration watchers, on install and when upgrading from before this version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes gaps that reading Omarchy PR #16100 (omacom/omarchy) showed here, and takes two more update paths out of the way of a second administrator.
Migrations
omarchy-mu-migrate-record@<admin>.pathwas only enabled by hand at install, so limited accounts could wait for good on an administrator added later. It now follows wheel (omarchy-mu-accounts sync-migration-watchers).omarchy-mu-migrate, under the machine-wide lock.Accounts
omarchy-mu-user-removerefuses system accounts, keeps a home holding an unfinished disk password change's note, and logs out an account with programs running, lingering included, before anything changes. Whenuserdelremoves the account but not its home, the rest still finishes.omarchy-mu-user-addrefuses a name whose group or/homefolder exists.omarchy-mu-user-admin offfails instead of saying the rights are gone whensudo -l -Ustill shows full sudo or the account is indocker.Update log
omarchy-mu-update-log.pathmoves a finished update's log to/tmp/omarchy-update.log.<owner>, also for updates started from the bar. The package enables it, and the watchers, on install and when upgrading from before 0.7.0.Behavior change
omarchy-mu-user-remove <user>used to delete the home. Without an option it now asks, and keeping is the default answer.--delete-homeis new.Testing
just testpassed with exit 0 in anarchlinuxcontainer, as in CI, with all the changes together: 116 shell tests, 19 JS tests, shellcheck, qmllint, the greeter smoke test and sudoers.The new tests fail against the old code, checked before the baseline fix was added. The account commands and the log script also ran in the container with real
useradd,userdel,sudo -l -U,pkillandscript(1), also before that fix.Not tested on a real Omarchy install: the notice on screen, systemd triggering the path unit (only
systemd-analyze verify), and the originalfs.protected_regularfailure.Known limits
omarchy-updateoutside the machine-wide lock, until Log the update transcript to a per-user path omacom/omarchy#15683 and #16100 merge upstream.The tag is left for after the merge:
just release 0.7.0signs it with the Yubikey.🤖 Generated with Claude Code