Skip to content

omamobile-omarchy 0.1.34: omamobile-update check refuses an update pacman can't plan (#433) - #478

Merged
derekross merged 1 commit into
mainfrom
update-check-plan
Nov 7, 2026
Merged

derekross merged 1 commit into
mainfrom
update-check-plan

Conversation

@derekross

@derekross derekross commented Nov 7, 2026 •

Copy link
Copy Markdown
Owner

As promised on #433. omamobile-update check ignored a failed pacman -Sup and 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

…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>
@derekross
derekross merged commit 1b440c1 into main Nov 7, 2026
2 checks passed
@derekross
derekross deleted the update-check-plan branch November 7, 2026 14:28
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant