nevaforget/moonarch-pkgbuilds
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: trim README to registry-only flow, log CI zombie-fix decisions

Browse Source 
README now describes the Gitea Arch registry path as the canonical
install/update mechanism — the paru --pkgbuilds fallback is no longer
advertised to users. Adds troubleshooting for missing updates (check
the repo DB directly) and file conflicts.

DECISIONS.md records why the build-and-publish workflow now wipes all
existing versions before upload, and why three packages had to be
re-registered manually.
This commit is contained in:
nevaforget
2026-04-20 14:15:44 +02:00
parent c2ccdccff4
commit 675c8bee45
2 changed files with 49 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+36 -17
View File
@@ -1,6 +1,7 @@
# Moonarch PKGBUILDs
Arch Linux package builds for the Moonarch ecosystem. Use with [paru](https://github.com/Morganamilo/paru) as a custom AUR source.
PKGBUILDs for the Moonarch ecosystem. Published as prebuilt Arch packages
via the Gitea Package Registry at `gitea.moonarch.de`.
## Packages
@@ -14,20 +15,16 @@ Arch Linux package builds for the Moonarch ecosystem. Use with [paru](https://gi
## Setup
Add to `~/.config/paru/paru.conf`:
The Moonarch installer configures `/etc/pacman.conf` with:
```ini
[moonarch]
Url = https://gitea.moonarch.de/nevaforget/moonarch-pkgbuilds
SigLevel = Required DatabaseOptional
Server = https://gitea.moonarch.de/api/packages/nevaforget/arch/$repo/$arch
```
Then sync the repository index:
```bash
paru -Sy --pkgbuilds
```
This downloads the PKGBUILDs from Gitea. Without this step, paru will not find the moonarch packages.
No extra paru setup required — `pacman` and `paru` both resolve moonarch
packages from the registry.
## Install
@@ -37,19 +34,41 @@ paru -S moonarch-git # pulls in all ecosystem packages as dependencies
## Update
Standard system upgrade picks up new versions automatically:
```bash
paru -Syu
```
Version bumps land in the registry automatically:
1. Push on `main` of `moonarch`, `moongreet`, `moonlock`, or `moonset`
triggers the per-project `update-pkgver.yaml` — pkgver-bot commits a
fresh `pkgver` to the matching PKGBUILD here.
2. That commit triggers `build-and-publish.yaml` (this repo): the runner
builds every changed PKGBUILD and uploads the artifacts to the Arch
registry. Before each upload all existing versions of the package are
deleted so the repo DB stays clean — see `build-and-publish.yaml` for
the rationale (zombie DB entries after pkgver changes).
`sweet-cursors-git` has no upstream CI; bump its `pkgrel` manually when
a rebuild is needed.
## Troubleshooting
**"not downloaded (use -Sy --pkgbuilds to download)"**: Run `paru -Sy --pkgbuilds` to fetch the repo index.
**"cannot update the lock file ... --locked was passed"**: The PKGBUILD cache is stale. Clear it and retry:
**`paru -Syu` shows no update even though a new version was published**:
check the repo DB has the new version.
```bash
rm -rf ~/.cache/paru/clone/repo/moonarch
paru -Sy --pkgbuilds && paru -S <package>
curl -s https://gitea.moonarch.de/api/packages/nevaforget/arch/moonarch/x86_64/moonarch.db \
| tar -tz | grep <pkgname>
```
If only an old version appears there, the `build-and-publish` workflow
did not run cleanly — inspect the latest run under
`gitea.moonarch.de/nevaforget/moonarch-pkgbuilds/actions`.
**File conflict on install** (`foo/bar exists in filesystem`): the file
was placed manually before the package claimed ownership. Once:
```bash
paru -Syu --overwrite=/path/to/conflicting/file
```