Repository navigation
omamobile-device-cheetah 0.1.51: the boot files with /run mounted 0755 reach installed phones - #667
Merged
Merged
Conversation
…5 reach installed phones The device package carries the 7 Pro's initramfs for omamobile-boot-update (RELEASES 5.1). #437 changed the initramfs (/run is mounted mode 0755, which Omarchy 4.5's update requires, #447) and the boot files were staged again, but the package's contents changed under the same version, and the build skips a version it has already built: phones installed from a release would have kept the old initramfs. A new version publishes it. No file in the package's source changes. The initramfs was booted on the Pixel 7 Pro on 2026-11-11 (7.3.0-rc6-omamobile-push1-gc7fb37460f84, pushed from the laptop): /run reads 755 and tools/phone-smoke passes. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
derekross
added a commit
that referenced
this pull request
Nov 12, 2026
…bers #403's reboot-to needs (#683) #403 changed src/reboot-to.c in every device package, but four of them had no new number on its branch: main had moved to the same one, or the branch never bumped it. Without a new number the build keeps the old package, so those phones would not get the reboot-to that notes a deliberate restart. Three of the four here. Their packages carry no boot image, so the bump only rebuilds the binary. device-cheetah stays at 0.1.51 on purpose. Its package carries the Pixel 7 Pro's boot image, which release phones write to slot B at the update, and the image's inputs have changed twice since the last one that booted (#667): initramfs/init (#562) and reboot-to.c (#403). It gets 0.1.52 once an image built from this tree has booted on the 7 Pro, as 0.1.51 did. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
7 of 8 tasks
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…5 reach installed phones (derekross#667) The device package carries the 7 Pro's initramfs for omamobile-boot-update (RELEASES 5.1). derekross#437 changed the initramfs (/run is mounted mode 0755, which Omarchy 4.5's update requires, derekross#447) and the boot files were staged again, but the package's contents changed under the same version, and the build skips a version it has already built: phones installed from a release would have kept the old initramfs. A new version publishes it. No file in the package's source changes. The initramfs was booted on the Pixel 7 Pro on 2026-11-11 (7.3.0-rc6-omamobile-push1-gc7fb37460f84, pushed from the laptop): /run reads 755 and tools/phone-smoke passes. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…bers derekross#403's reboot-to needs (derekross#683) derekross#403 changed src/reboot-to.c in every device package, but four of them had no new number on its branch: main had moved to the same one, or the branch never bumped it. Without a new number the build keeps the old package, so those phones would not get the reboot-to that notes a deliberate restart. Three of the four here. Their packages carry no boot image, so the bump only rebuilds the binary. device-cheetah stays at 0.1.51 on purpose. Its package carries the Pixel 7 Pro's boot image, which release phones write to slot B at the update, and the image's inputs have changed twice since the last one that booted (derekross#667): initramfs/init (derekross#562) and reboot-to.c (derekross#403). It gets 0.1.52 once an image built from this tree has booted on the 7 Pro, as 0.1.51 did. Co-authored-by: Claude Fable 5.2 <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.
Follow-up to #437, and a step of the move to Omarchy 4.5 (#434, #447).
Why
The device package carries the 7 Pro's initramfs for
omamobile-boot-update. #437 changed the initramfs (/runmounted mode 0755) and the boot files were staged again, but the package's contents changed under the same version, 0.1.50, and the build skips a version it has already built. Phones installed from a release would have kept the old initramfs, with/runat 1777, and Omarchy 4.5's update stops on that.What
The version line only. No file in the package's source changes.
Tested
7.3.0-rc6-omamobile-push1-gc7fb37460f84), pushed from the laptop:/run,/run/lockand/run/userread 755, no failed unit,tools/phone-smokepassed.tools/stage-boot-files --check).packages/omamobile-device-cheetah/test/all,tools/pr-check.Not tested
The package's own path onto a phone: a release-installed phone taking 0.1.51 through
omarchy update, where the pacman hook writes slot B. That is the next attended step on the 7 Pro.Note for #403: it also writes 0.1.51 and takes 0.1.52 after this.
🤖 Generated with Claude Code