Please include Omawrite in Try Omarchy's ARM64 factory image so it is available from the application launcher after first-boot provisioning.
The proposed approach follows the existing pinned ttfx integration: build verified upstream source for ARM64, install a Pacman-owned package, and retain it in the guest's immutable local repository.
The official omarchy-pkgs recipe already declares aarch64 support for Omawrite 0.5.0.
Proposed integration
- Pin Omawrite 0.5.0 source, archive and license hashes, compiler/Qt versions, and the measured ARM64 binary hash under
supplyChain.omawrite.
- Add a native Qt 6/qmake build helper, following the ttfx helper's interface and source-verification pattern.
- Install
try-omarchy-omawrite, providing omawrite=0.5.0 and conflicting with omawrite. Include the desktop entry, icon, MIT license, and bundled font's OFL license.
- Register the package before sealing the local repository, increasing its expected package count from five to six.
- Explicitly request
qt6-base, qt6-declarative, hicolor-icon-theme, and xdg-desktop-portal. All four already exist in the reviewed dependency lock.
- Verify ARM64 ELF identity, binary checksum, package ownership/integrity, dependency satisfaction, and headless Qt startup. Update documentation and third-party notices.
This targets fresh factory-based VMs. Existing persistent disks would keep their contents; automatic migration and upstream Omawrite changes are outside this request.
Local implementation and verification
A local implementation has been prepared, but its code has not been published in a branch or PR.
- Two ARM64 builds under emulation produced byte-identical executables.
- Binary SHA-256:
c6c13d551c57a719eb516b16ccf83d0e4addd9a172f271dfd3ca744c09aefdd3.
- Package assembly produced byte-identical archives across separate staging directories.
- All 12 upstream Qt tests, 10 new integration-validation tests, and guest contract checks passed.
- Package installation and integrity checks passed. That run exposed an ownership-query bug, now corrected to run Pacman inside the staged guest; the corrected installation/startup/reinstallation sequence still needs a complete rerun.
Acceptance criteria and remaining verification
The attempted full builder stopped because its existing rust=1:1.98.0-1 pin was unavailable from the configured mirror. Three boot-export test failures were also reproduced against an untouched checkout on the Linux validation host. These remain separate from the Omawrite change; the Apple Silicon GUI checks have not yet been performed.
Please include Omawrite in Try Omarchy's ARM64 factory image so it is available from the application launcher after first-boot provisioning.
The proposed approach follows the existing pinned ttfx integration: build verified upstream source for ARM64, install a Pacman-owned package, and retain it in the guest's immutable local repository.
The official omarchy-pkgs recipe already declares
aarch64support for Omawrite 0.5.0.Proposed integration
supplyChain.omawrite.try-omarchy-omawrite, providingomawrite=0.5.0and conflicting withomawrite. Include the desktop entry, icon, MIT license, and bundled font's OFL license.qt6-base,qt6-declarative,hicolor-icon-theme, andxdg-desktop-portal. All four already exist in the reviewed dependency lock.This targets fresh factory-based VMs. Existing persistent disks would keep their contents; automatic migration and upstream Omawrite changes are outside this request.
Local implementation and verification
A local implementation has been prepared, but its code has not been published in a branch or PR.
c6c13d551c57a719eb516b16ccf83d0e4addd9a172f271dfd3ca744c09aefdd3.Acceptance criteria and remaining verification
The attempted full builder stopped because its existing
rust=1:1.98.0-1pin was unavailable from the configured mirror. Three boot-export test failures were also reproduced against an untouched checkout on the Linux validation host. These remain separate from the Omawrite change; the Apple Silicon GUI checks have not yet been performed.