Repository navigation
omamobile-omarchy 0.1.34: omamobile-update check refuses an update pacman can't plan (#433) - #478
Merged
Merged
Conversation
…cman can't plan (#433) omamobile-update check asks pacman for the whole update's plan (pacman -Sup) to see what it would install, but it ignored a failed plan and fell back to checkupdates' plain list. So when the plan can't be made, check said ok and the update sheet offered an update that then stopped partway. On #433, a phone installed before 2026-11-03 hit this: [omarchy]'s aquamarine 0.15.1 lacks the libaquamarine.so=15 our Hyprland needs. A failed plan, or one that can't run, is now a blocker that quotes pacman's own error lines. A test feeds the fake pacman #433's real message and checks the refusal and the reason; with the old code it fails. The package's test/all: 230 ok. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 7, 2026
derekross
added a commit
that referenced
this pull request
Nov 7, 2026
… the titlebars migration is held (#469) (#486) omamobile-update keeps its phone-critical migration holds on even when OMAMOBILE_HOLD_MIGRATIONS turns the generic holds off, and only an explicit 0 turns those off. Migration 1791403310 (omarchy-hyprland-titlebars, which pins an exact Hyprland and stopped a real 7 Pro's update on #433) is held by number and by pattern: any migration installing a package in rootfs/packages.omarchy-skip. Named holds say why in their own words. Merged as 0.1.35 because #478 shipped 0.1.34. Co-Authored-By: Marsel Nenaj <201385099+marselnenaj@users.noreply.github.com> Co-Authored-By: Codex <codex@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…cman can't plan (derekross#433) (derekross#478) omamobile-update check asks pacman for the update's plan (pacman -Sup) but ignored a failed plan and fell back to checkupdates' plain list, so it said ok and the update sheet offered an update that then stopped partway. That happened on phones installed before 2026-11-03, where [omarchy]'s aquamarine 0.15.1 lacks the libaquamarine.so=15 our Hyprland needs (derekross#433). A failed plan, or one that can't run, is now a blocker that quotes pacman's own error lines. A test feeds derekross#433's real message and fails against the old code; test/all: 230 ok. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
… the titlebars migration is held (derekross#469) (derekross#486) omamobile-update keeps its phone-critical migration holds on even when OMAMOBILE_HOLD_MIGRATIONS turns the generic holds off, and only an explicit 0 turns those off. Migration 1791403310 (omarchy-hyprland-titlebars, which pins an exact Hyprland and stopped a real 7 Pro's update on derekross#433) is held by number and by pattern: any migration installing a package in rootfs/packages.omarchy-skip. Named holds say why in their own words. Merged as 0.1.35 because derekross#478 shipped 0.1.34. Co-Authored-By: Marsel Nenaj <201385099+marselnenaj@users.noreply.github.com> Co-Authored-By: Codex <codex@openai.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.
As promised on #433.
omamobile-update checkignored a failedpacman -Supand fell back to checkupdates' list, so it said ok for an update pacman can't plan, and the update then stopped partway. That's what happened on pre-11-03 phones with Omarchy's aquamarine 0.15.1.Now a failed plan is a blocker that quotes pacman's reason. The new test uses #433's real message, and it fails against the old code.
test/all: 230 ok.It changes the update sheet's check on the 7 Pro only when pacman can't plan the update; any update that plans works as before. #469 claims 0.1.33, which #431 took, so it will get the next free version at merge.
🤖 Generated with Claude Code