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-1235GitHub issuePublicDecided· Out of scope

stable-mirror.omarchy.org Arch repo databases stale (~5 days behind)

Reported by a-lang · filed Aug 30, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 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

stable-mirror.omarchy.org Arch repo databases stale (~5 days behind)revision 1 · captured 2026-09-28 21:24 UTC via poll

System details

AMD Ryzen 7 7735HS, Red Hat Virtio 1.0 GPU (QEMU/KVM VM), Omarchy 4.0.1-1 (stable channel), kernel 7.1.9-arch1-2

What's wrong?

The Arch mirror used by default in /etc/pacman.d/mirrorlist — stable-mirror.omarchy.org — has not synced its core/extra/multilib databases since 2026-08-25 11:05:38 UTC (~5 days stale). Official Arch mirrors are at 2026-08-30 02:26 UTC. Packages added to Arch repos after Aug 25 are invisible to pacman -Ss.

Steps to recreate

  1. pacman -Ss gradia → no results, even though the package exists in extra (https://archlinux.org/packages/extra/x86_64/gradia/, gradia 1.13.0-1, built 2026-08-26).
  2. omarchy update runs pacman -Syu without error, but the log shows extra is up to date under :: Synchronizing package databases... — pacman only re-downloads a db when the server's copy is newer, so a stale mirror is silently accepted.
  3. Compare the mirror's db freshness against official:
$ curl -sI https://stable-mirror.omarchy.org/extra/os/x86_64/extra.db | grep -i last-modified
last-modified: Tue, 25 Aug 2026 11:05:38 GMT

$ curl -sI https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db | grep -i last-modified
last-modified: Sun, 30 Aug 2026 02:26:13 GMT

All three Arch repos on the mirror are affected:

core:      Tue, 25 Aug 2026 11:05:38 GMT
extra:     Tue, 25 Aug 2026 11:05:38 GMT
multilib:  Tue, 25 Aug 2026 11:05:37 GMT

Expected: stable-mirror.omarchy.org Arch repo databases sync regularly so pacman -Ss finds current packages.

Actual: databases stuck at 2026-08-25 11:05 UTC; pacman -Syu reports "up to date" while the local db misses recent packages. Any package added after 2026-08-25 is unfindable unless the user switches to an official mirror.

Impact: mirror is stale for all Arch repos; pkgs.omarchy.org (the omarchy package repo, channel stable) is unaffected and current (2026-08-29 16:14 UTC).

View raw text
### System details

AMD Ryzen 7 7735HS, Red Hat Virtio 1.0 GPU (QEMU/KVM VM), Omarchy 4.0.1-1 (stable channel), kernel 7.1.9-arch1-2

### What's wrong?

The Arch mirror used by default in `/etc/pacman.d/mirrorlist` — `stable-mirror.omarchy.org` — has not synced its `core`/`extra`/`multilib` databases since **2026-08-25 11:05:38 UTC** (~5 days stale). Official Arch mirrors are at 2026-08-30 02:26 UTC. Packages added to Arch repos after Aug 25 are invisible to `pacman -Ss`.

**Steps to recreate**

1. `pacman -Ss gradia` → no results, even though the package exists in extra (https://archlinux.org/packages/extra/x86_64/gradia/, `gradia` 1.13.0-1, built 2026-08-26).
2. `omarchy update` runs `pacman -Syu` without error, but the log shows `extra is up to date` under `:: Synchronizing package databases...` — pacman only re-downloads a db when the server's copy is newer, so a stale mirror is silently accepted.
3. Compare the mirror's db freshness against official:

```
$ curl -sI https://stable-mirror.omarchy.org/extra/os/x86_64/extra.db | grep -i last-modified
last-modified: Tue, 25 Aug 2026 11:05:38 GMT

$ curl -sI https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db | grep -i last-modified
last-modified: Sun, 30 Aug 2026 02:26:13 GMT
```

All three Arch repos on the mirror are affected:

```
core:      Tue, 25 Aug 2026 11:05:38 GMT
extra:     Tue, 25 Aug 2026 11:05:38 GMT
multilib:  Tue, 25 Aug 2026 11:05:37 GMT
```

**Expected**: `stable-mirror.omarchy.org` Arch repo databases sync regularly so `pacman -Ss` finds current packages.

**Actual**: databases stuck at 2026-08-25 11:05 UTC; `pacman -Syu` reports "up to date" while the local db misses recent packages. Any package added after 2026-08-25 is unfindable unless the user switches to an official mirror.

**Impact**: mirror is stale for all Arch repos; `pkgs.omarchy.org` (the omarchy package repo, channel `stable`) is unaffected and current (2026-08-29 16:14 UTC).

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 10:02 UTC