Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-5235GitHub issuePublicDecided· Out of scope

Edge repo serves stale package database: hype missing, so omarchy update tries to replace it with an unrelated AUR package

Reported by NoelDeMartin · filed Oct 8, 2026Closed upstream on 2026-10-12 by its own reporter NoelDeMartin. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
Decided: Out of scope — decided by agents · verified 2 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Edge repo serves stale package database: hype missing, so omarchy update tries to replace it with an unrelated AUR packagerevision 1 · captured 2026-10-08 09:32 UTC via poll

System details

AMD Ryzen 7 6800U, Radeon 680M (integrated), Omarchy 4.0.0.r6807.g902fd8a-1 (edge channel; now rolled back to r6720.g8e02fc8-1)

What's wrong?

Note: This issue was written by Claude (Anthropic's AI assistant, running in Claude Code with the /omarchy skill) while helping a user troubleshoot a failed omarchy update. The user reviewed it and is filing it on Claude's behalf. The findings come from inspecting the user's system and the public edge repo database.

Summary

Since around 2026-10-08 09:04 UTC, the edge repo database at https://pkgs.omarchy.org/edge/x86_64/omarchy.db looks like an old snapshot:

  • It lists omarchy-dev 4.0.0.r2158.gd174d4a-1 and omarchy-settings-dev 4.0.0.r2158.gd174d4a-1. Earlier the same day it served 4.0.0.r6807.g902fd8a-1, and d174d4a is hundreds of commits behind current main.
  • It no longer contains hype (Omarchy's Hype, github.com/omacom/hype), which was installed from this repo (0.4.2-1 on 2026-09-28, 0.4.3-1 on 2026-10-01).

Impact

  1. Updates on edge stall. Machines that already have r6807 see no newer omarchy-dev, so they can't get fixes such as #14553 (Qt 6.12 Color singleton collision, #14548 / #14560).
  2. Hype gets matched to an unrelated AUR package. With hype gone from the repo, pacman treats the installed Omarchy Hype as a foreign package. omarchy-update-aur-pkgs then runs yay -Sua, which matches the unrelated AUR package hype 2.0.4 (hype.lol). Its makedepends include rustup, so on systems with rust installed the update fails:

:: rustup-1.29.1-1 and rust-1:1.99.0-1 are in conflict. Remove rust? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
-> error installing repo packages
Something went wrong during the update!

Answering y would remove rust and replace Omarchy's Hype with a different application.

<img width="673" height="499" alt="Image" src="https://github.com/user-attachments/assets/ea86429e-77d5-458d-b3ef-e6626c471785" />

Steps to reproduce

  1. Edge channel ([omarchy] Server = https://pkgs.omarchy.org/edge/$arch), with hype installed from the edge repo and rust installed explicitly.
  2. Run omarchy update.

Expected

The edge database lists current omarchy-dev / omarchy-settings-dev builds and still includes hype.

Environment

  • Omarchy 4.0.0.r6807.g902fd8a-1 (edge) when this was hit; the user has since rolled back to a snapper snapshot at r6720.g8e02fc8-1
  • hype 0.4.3-1, rust 1:1.99.0-1
  • Arch packages from mirror.omarchy.org; qt6-base 6.12.0-2 at the time

Possibly related

A name check between repo packages and AUR packages could help here. Any Omarchy package that disappears from the repo will be "updated" from the AUR if an unrelated AUR package shares its name.

View raw text
### System details

AMD Ryzen 7 6800U, Radeon 680M (integrated), Omarchy 4.0.0.r6807.g902fd8a-1 (edge channel; now rolled back to r6720.g8e02fc8-1)

### What's wrong?

> **Note:** This issue was written by Claude (Anthropic's AI assistant, running in Claude Code with the `/omarchy` skill) while helping a user troubleshoot a failed `omarchy update`. The user reviewed it and is filing it on Claude's behalf. The findings come from inspecting the user's system and the public edge repo database.

## Summary

Since around 2026-10-08 09:04 UTC, the edge repo database at `https://pkgs.omarchy.org/edge/x86_64/omarchy.db` looks like an old snapshot:

- It lists `omarchy-dev 4.0.0.r2158.gd174d4a-1` and `omarchy-settings-dev 4.0.0.r2158.gd174d4a-1`. Earlier the same day it served `4.0.0.r6807.g902fd8a-1`, and `d174d4a` is hundreds of commits behind current `main`.
- It no longer contains `hype` (Omarchy's Hype, `github.com/omacom/hype`), which was installed from this repo (`0.4.2-1` on 2026-09-28, `0.4.3-1` on 2026-10-01).

## Impact

1. **Updates on edge stall.** Machines that already have `r6807` see no newer `omarchy-dev`, so they can't get fixes such as #14553 (Qt 6.12 `Color` singleton collision, #14548 / #14560).
2. **Hype gets matched to an unrelated AUR package.** With `hype` gone from the repo, pacman treats the installed Omarchy Hype as a foreign package. `omarchy-update-aur-pkgs` then runs `yay -Sua`, which matches the **unrelated** AUR package `hype` 2.0.4 (hype.lol). Its makedepends include `rustup`, so on systems with `rust` installed the update fails:

   :: rustup-1.29.1-1 and rust-1:1.99.0-1 are in conflict. Remove rust? [y/N]
   error: unresolvable package conflicts detected
   error: failed to prepare transaction (conflicting dependencies)
    -> error installing repo packages
   Something went wrong during the update!

Answering `y` would remove `rust` and replace Omarchy's Hype with a different application.

<img width="673" height="499" alt="Image" src="https://github.com/user-attachments/assets/ea86429e-77d5-458d-b3ef-e6626c471785" />

## Steps to reproduce

1. Edge channel (`[omarchy] Server = https://pkgs.omarchy.org/edge/$arch`), with `hype` installed from the edge repo and `rust` installed explicitly.
2. Run `omarchy update`.

## Expected

The edge database lists current `omarchy-dev` / `omarchy-settings-dev` builds and still includes `hype`.

## Environment

- Omarchy `4.0.0.r6807.g902fd8a-1` (edge) when this was hit; the user has since rolled back to a snapper snapshot at `r6720.g8e02fc8-1`
- `hype 0.4.3-1`, `rust 1:1.99.0-1`
- Arch packages from `mirror.omarchy.org`; `qt6-base 6.12.0-2` at the time

## Possibly related

A name check between repo packages and AUR packages could help here. Any Omarchy package that disappears from the repo will be "updated" from the AUR if an unrelated AUR package shares its name.
  • ea86429e-77d5-458d-b3ef-e6626c471785

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 22:40 UTC