716c77f93b
All checks were successful
Build and publish python-pywal / python-pywal (push) Successful in 1m21s
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".
19 lines
1 KiB
Markdown
19 lines
1 KiB
Markdown
Arch packaging
|
|
==============
|
|
|
|
This directory only holds `PKGBUILD`s for third-party AUR packages BOS
|
|
republishes to the `[breadway]` pacman repo (`calamares`, `bibata`,
|
|
`powerlevel10k`, `yay-bin`, `python-pywal`) — not the user's own code. See each
|
|
subdirectory's `.forgejo/workflows/<name>.yml` (in this repo) for how each
|
|
one publishes on a push to `packaging/<name>/**`.
|
|
|
|
Every bread-ecosystem app (bakery, bread, breadbar, breadbox, breadcrumbs,
|
|
breadpad, breadpaper, breadmon, breadsearch, breadclip, breadshot,
|
|
bos-settings, breadhelp, ...) is bakery-managed, not pacman-packaged — see
|
|
`iso/bread-lockfile.toml` (`required_bins` + `optional_bins`), which
|
|
`build-local.sh` uses as the name list when baking this machine's bakery
|
|
install into the ISO's `/etc/skel`.
|
|
`breadlock` is the sole deliberate exception (it needs a root-owned
|
|
`/etc/pam.d/breadlock` PAM service file, which bakery — by design — has no
|
|
privileged-install path for) and stays on pacman only; see
|
|
`bread-ecosystem/docs/release-channels.md` for the full policy.
|