Skip to content

packages.pinned: hold Omarchy at 4.5.0-3, the version the 4.5 series was checked against - #670

Merged
derekross merged 1 commit into
mainfrom
omarchy-45-pin
Nov 11, 2026
Merged

derekross merged 1 commit into
mainfrom
omarchy-45-pin

Conversation

@derekross

Copy link
Copy Markdown
Owner

Moves [omamobile]'s pins for omarchy and omarchy-settings from 4.0.6-1 to 4.5.0-3. Once this is published, a phone on the development channel takes Omarchy 4.5 at its next omarchy update.

Why now

The pins went in on 2026-11-06 because the patch series didn't apply to 4.5 and 4.5's migrations could install packages that replace ours (#433, #434). What that needed is merged: the 4.5 family's last two ports (#661), the renamed and dropped commands (#662), the composed package list (#665) and the notification store (#482).

Why a pin and not no pin

The pin moves rather than goes, so a phone takes a newer Omarchy only after the series was checked against it. For a later Omarchy, these two lines move again.

Evidence

  • Rehearsal image: 4.0.6 to 4.5.0-3, in one step and in two, with the update's own --overwrite.
  • A root image built on 4.5.0-3 and smoke-tested.
  • Pixel 7 Pro, 2026-11-11, through the Updates sheet: exit 0, 28 patches verified, 98 migrations (24 held, none failed), restart from the sheet, tools/phone-smoke passing afterwards.
  • The maintainer's hands-on checklist on that phone passes: lock (PIN pad, glance, fingerprint, emergency, double tap to wake), notifications (shade, badge, swipe, Clear all), screenshot, menu and About, Mic dictation, sleep and wake, Updates sheet.
  • Both package files: SHA-256 as listed, good signature from Omarchy's key (pacman-key --verify).
  • tests/all, tests/pinned-packages and packages/omamobile-omarchy/test/all pass.

Also

AGENTS.md, README.md and docs/RELEASES.md §5.4 now say phones run the 4.5 family and that legacy-4.0.6/ serves a phone that hasn't updated yet. Removing legacy-4.0.6/ is a later change, after stable phones have moved.

Closes #434.

🤖 Generated with Claude Code

…was checked against

[omamobile] held omarchy and omarchy-settings at 4.0.6 while the patch
series didn't apply to 4.5 (#433, #434). The 4.5 family, the update's
stand-ins and the held migrations are in (#661, #662, #665, #482), a
rehearsal image updated from 4.0.6 in one and in two steps, and the
7 Pro took the update through its Updates sheet on 2026-11-11: exit 0,
28 patches verified, 98 migrations with 24 held and none failed,
phone-smoke passing after the restart.

The pin moves rather than goes: a phone takes a newer Omarchy only after
the series was checked against it. Phones on 4.0.6 move to 4.5.0-3 at
their next omarchy update; legacy-4.0.6/ stays for them until then.

Both files were checked against upstream's signatures.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross
derekross merged commit bb02e11 into main Nov 11, 2026
2 checks passed
@derekross
derekross deleted the omarchy-45-pin branch November 11, 2026 22:22
derekross added a commit that referenced this pull request Nov 12, 2026
…s run (#673)

Omarchy 4.5 refuses to work under a /run that anyone can write: its sudo
migration (1788163635) exits 1, which stops omarchy update, and its
pacman hooks abort later transactions (#447). Boot images from before
#437 mount /run with tmpfs's default, 1777. A phone gets a new boot
image only through a restart, and only the Pixel 7 Pro's device package
carries one, so with Omarchy pinned at 4.5.0-3 (#670) a release-installed
7 Pro stops in its first update to 4.5 until it is restarted and updated
again, and every other phone stops at each attempt until its owner
rebuilds and pushes boot images. The 7 Pro that took the update on
2026-11-11 had the new image pushed first, so it didn't show this; the
round 52 review of #670 found it.

A tmpfiles.d rule, z /run 0755 root root. pacman's own tmpfiles hook
(21-systemd-tmpfiles.hook, PostTransaction) applies it in the transaction
that installs it, which is before Omarchy's migrations, and
systemd-tmpfiles-setup applies it at every boot, on every device and
whatever the boot image.

On the Pixel 7 Pro (Omarchy 4.5.0-3): with /run set to 1777, Omarchy's
omarchy_security_assert_root_directory /run 755 refuses; after
systemd-tmpfiles --create with this file /run is 755 root and it passes;
a 0700 directory inside a scratch /run keeps its mode. Not run: a whole
update from 4.0.6 on a phone booted from an old image.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 12, 2026
…#678)

Omarchy 4.5's package list, which build-rootfs now composes (#665), adds
26 packages to an image over 4.0.6's. Three kinds don't belong in a
phone image:

- superwhisper-bin is proprietary (LicenseRef-proprietary, 184 MiB), and
  images carry no proprietary preinstalls. The 4.5 test image built on
  2026-11-11 had it (its MANIFEST lists superwhisper-bin 1.3.0-1); that
  image was never released.
- owe, the video wallpaper engine: the migration that starts it is held
  on updated phones, so a new image would differ from an updated phone
  in exactly that.
- five fcitx5 engines: the on-screen keyboard holds the input-method slot
  and the Fcitx migration is held, so nothing could use them.

None is a dependency of omarchy or omarchy-settings 4.5.0-3; they are
only in the list. Found by the round 52 review of #665 and #670.

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
…was checked against (derekross#670)

[omamobile] held omarchy and omarchy-settings at 4.0.6 while the patch
series didn't apply to 4.5 (derekross#433, derekross#434). The 4.5 family, the update's
stand-ins and the held migrations are in (derekross#661, derekross#662, derekross#665, derekross#482), a
rehearsal image updated from 4.0.6 in one and in two steps, and the
7 Pro took the update through its Updates sheet on 2026-11-11: exit 0,
28 patches verified, 98 migrations with 24 held and none failed,
phone-smoke passing after the restart.

The pin moves rather than goes: a phone takes a newer Omarchy only after
the series was checked against it. Phones on 4.0.6 move to 4.5.0-3 at
their next omarchy update; legacy-4.0.6/ stays for them until then.

Both files were checked against upstream's signatures.

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
…s run (derekross#673)

Omarchy 4.5 refuses to work under a /run that anyone can write: its sudo
migration (1788163635) exits 1, which stops omarchy update, and its
pacman hooks abort later transactions (derekross#447). Boot images from before
derekross#437 mount /run with tmpfs's default, 1777. A phone gets a new boot
image only through a restart, and only the Pixel 7 Pro's device package
carries one, so with Omarchy pinned at 4.5.0-3 (derekross#670) a release-installed
7 Pro stops in its first update to 4.5 until it is restarted and updated
again, and every other phone stops at each attempt until its owner
rebuilds and pushes boot images. The 7 Pro that took the update on
2026-11-11 had the new image pushed first, so it didn't show this; the
round 52 review of derekross#670 found it.

A tmpfiles.d rule, z /run 0755 root root. pacman's own tmpfiles hook
(21-systemd-tmpfiles.hook, PostTransaction) applies it in the transaction
that installs it, which is before Omarchy's migrations, and
systemd-tmpfiles-setup applies it at every boot, on every device and
whatever the boot image.

On the Pixel 7 Pro (Omarchy 4.5.0-3): with /run set to 1777, Omarchy's
omarchy_security_assert_root_directory /run 755 refuses; after
systemd-tmpfiles --create with this file /run is 755 root and it passes;
a 0700 directory inside a scratch /run keeps its mode. Not run: a whole
update from 4.0.6 on a phone booted from an old image.

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
…derekross#678)

Omarchy 4.5's package list, which build-rootfs now composes (derekross#665), adds
26 packages to an image over 4.0.6's. Three kinds don't belong in a
phone image:

- superwhisper-bin is proprietary (LicenseRef-proprietary, 184 MiB), and
  images carry no proprietary preinstalls. The 4.5 test image built on
  2026-11-11 had it (its MANIFEST lists superwhisper-bin 1.3.0-1); that
  image was never released.
- owe, the video wallpaper engine: the migration that starts it is held
  on updated phones, so a new image would differ from an updated phone
  in exactly that.
- five fcitx5 engines: the on-screen keyboard holds the input-method slot
  and the Fcitx migration is held, so nothing could use them.

None is a dependency of omarchy or omarchy-settings 4.5.0-3; they are
only in the list. Found by the round 52 review of derekross#665 and derekross#670.

Co-authored-by: Claude Fable 5.2 <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.

omamobile-omarchy 0.1.32: the Omarchy patch series doesn't apply to omarchy 4.5.0-2 (build-rootfs fails)

1 participant