packaging: republish python-pywal to [breadway] #6

Merged

Breadway merged 2 commits from fix/republish-python-pywal into main

2026-08-31 19:18:38 +08:00

Breadway commented

2026-08-31 19:15:54 +08:00

Owner

Unblocks every BOS ISO build. python-pywal was dropped from Arch's [extra] (AUR-only now: 0 results in the official repos), so pacstrap fails with target not found: python-pywal — I hit this trying to build the F1 branch. The wal binary is load-bearing (bread-theme extracts the wallpaper palette with it).

Republished the same way as calamares / bibata / powerlevel10k / yay-bin:

packaging/python-pywal/PKGBUILD — in-house copy of the AUR PKGBUILD, modernised: python -m build / python -m installer instead of the removed setup.py install, sha256-only sources (matching the sibling PKGBUILDs). Test-built on hermes: 28 unit tests pass, package ships /usr/bin/wal + license.
.forgejo/workflows/python-pywal.yml — builds + PUTs to the Forgejo Arch registry on a push to packaging/python-pywal/** (mirrors bibata.yml).
signed-repo.yml gains it as a workflow_run trigger; ci-publish-signed-repo.sh gains it in PACKAGES so the signed dl.breadway.dev/arch db picks it up.
packages.x86_64 keeps the python-pywal line (now from [breadway]) with a note.

Ordering

python-pywal.yml must publish to the Forgejo registry once before signed-repo.yml runs, or its collect step errors registry db missing packages: python-pywal. After merge: let python-pywal.yml run (it triggers on the merge, path-scoped), then dispatch signed-repo.yml (or it chains via workflow_run).

Pairs with #5 (the [breadway] SigLevel = Required flip) — both are needed for a working build. F1's signing itself is already verified: the failed build got past breadway downloading... with the signed db verifying clean.

Unblocks every BOS ISO build. `python-pywal` was dropped from Arch's `[extra]` (AUR-only now: 0 results in the official repos), so `pacstrap` fails with `target not found: python-pywal` — I hit this trying to build the F1 branch. The `wal` binary is load-bearing (bread-theme extracts the wallpaper palette with it). Republished the same way as `calamares` / `bibata` / `powerlevel10k` / `yay-bin`: - **`packaging/python-pywal/PKGBUILD`** — in-house copy of the AUR PKGBUILD, modernised: `python -m build` / `python -m installer` instead of the removed `setup.py install`, sha256-only sources (matching the sibling PKGBUILDs). **Test-built on hermes**: 28 unit tests pass, package ships `/usr/bin/wal` + license. - **`.forgejo/workflows/python-pywal.yml`** — builds + `PUT`s to the Forgejo Arch registry on a push to `packaging/python-pywal/**` (mirrors `bibata.yml`). - **`signed-repo.yml`** gains it as a `workflow_run` trigger; **`ci-publish-signed-repo.sh`** gains it in `PACKAGES` so the signed `dl.breadway.dev/arch` db picks it up. - `packages.x86_64` keeps the `python-pywal` line (now from `[breadway]`) with a note. ## Ordering `python-pywal.yml` must publish to the Forgejo registry **once** before `signed-repo.yml` runs, or its collect step errors `registry db missing packages: python-pywal`. After merge: let `python-pywal.yml` run (it triggers on the merge, path-scoped), then dispatch `signed-repo.yml` (or it chains via `workflow_run`). Pairs with **#5** (the `[breadway]` `SigLevel = Required` flip) — both are needed for a working build. F1's signing itself is already verified: the failed build got past `breadway downloading...` with the signed db verifying clean.

Breadway added 2 commits 2026-08-31 19:15:54 +08:00

iso: add external-monitors bread module for zero-config docking b38bbbac1a

packaging: republish python-pywal to [breadway]

Build and publish python-pywal / python-pywal (push) Successful in 1m21s

Details

716c77f93b

python-pywal was dropped from Arch's [extra] repo (AUR-only now), so
`pacstrap` can no longer resolve it and every ISO build fails with
"target not found: python-pywal". The `wal` binary is load-bearing —
bread-theme shells out to it to extract the colour palette from the
user's wallpaper.

Republish it the same way as calamares / bibata / powerlevel10k /
yay-bin:

- `packaging/python-pywal/PKGBUILD` — in-house copy of the AUR PKGBUILD
  (Morten Linderud's), modernised to `python -m build` / `installer`
  instead of the removed `setup.py install`, sha256-only sources like
  the sibling PKGBUILDs. Test-built locally: 28 unit tests pass, package
  ships `/usr/bin/wal`.
- `.forgejo/workflows/python-pywal.yml` — builds + PUTs to the Forgejo
  Arch registry on a push to `packaging/python-pywal/**`.
- `signed-repo.yml` gains it as a `workflow_run` trigger;
  `ci-publish-signed-repo.sh` gains it in `PACKAGES` so the signed
  dl.breadway.dev/arch db picks it up.
- packages.x86_64 keeps the `python-pywal` line (now sourced from
  [breadway]) with a note.

Ordering: `python-pywal.yml` must publish to the registry once before
`signed-repo.yml` runs, or the collect step errors "registry db missing
packages: python-pywal".

Breadway merged commit e3cdf33f83 into main

2026-08-31 19:18:38 +08:00

Breadway referenced this pull request from a commit

2026-08-31 19:18:41 +08:00

Merge pull request 'packaging: republish python-pywal to [breadway]' (#6) from fix/republish-python-pywal into main

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Breadway/bos#6

No description provided.

Rows
Columns