Go to file

Build and publish packages / build-and-publish (push) Successful in 16m7s

Details

fix(pkg): declare gtk4 build deps for GTK rust apps

moongreet/moonlock/moonset link against gtk4 headers at build time.
The CI workflow runs `makepkg -sfd` and only installs makedepends
explicitly — with gtk4 listed only in depends, the build container
had no cairo.pc / gtk4.pc and cairo-sys-rs failed to find the
system library. Add gtk4, gtk4-layer-shell, pkgconf (plus
gtk-session-lock + pam for moonlock) to makedepends.

This previously only worked because repeated `makepkg -s` runs
left the libs installed in the act_runner container filesystem.
Recreating the runner today exposed the latent gap.

2026-04-21 10:03:22 +02:00

.gitea/workflows

fix(ci): wipe all existing versions before upload to kill zombie DB entries

2026-04-20 14:09:33 +02:00

moonarch-git

refactor(moonarch-git): hard-dep ecosystem + Arch essentials, pkgrel 10

2026-04-21 09:15:25 +02:00

moongreet-git

fix(pkg): declare gtk4 build deps for GTK rust apps

2026-04-21 10:03:22 +02:00

moonlock-git

fix(pkg): declare gtk4 build deps for GTK rust apps

2026-04-21 10:03:22 +02:00

moonset-git

fix(pkg): declare gtk4 build deps for GTK rust apps

2026-04-21 10:03:22 +02:00

sshfsc-git

chore(sshfsc-git): bump pkgver to 0.1.0.r2.gba89562

2026-04-19 13:30:16 +00:00

sweet-cursors-git

chore: bump pkgrel for moongreet/moonset/sweet-cursors

2026-04-20 13:36:05 +02:00

.gitignore

Update pkgver from first build, add .gitignore for build artifacts

2026-03-29 18:31:12 +02:00

DECISIONS.md

refactor(moonarch-git): hard-dep ecosystem + Arch essentials, pkgrel 10

2026-04-21 09:15:25 +02:00

README.md

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

2026-04-20 14:15:44 +02:00

README.md

Moonarch PKGBUILDs

PKGBUILDs for the Moonarch ecosystem. Published as prebuilt Arch packages via the Gitea Package Registry at gitea.moonarch.de.

Packages

Package	Description
`moonarch-git`	Desktop environment defaults (Niri, Waybar, Catppuccin Mocha)
`moonset-git`	Wayland session power menu
`moonlock-git`	Wayland lockscreen with PAM and fingerprint support
`moongreet-git`	greetd greeter for Wayland
`sweet-cursors-git`	Sweet cursor theme

Setup

The Moonarch installer configures /etc/pacman.conf with:

[moonarch]
SigLevel = Required DatabaseOptional
Server = https://gitea.moonarch.de/api/packages/nevaforget/arch/$repo/$arch

No extra paru setup required — pacman and paru both resolve moonarch packages from the registry.

Install

paru -S moonarch-git   # pulls in all ecosystem packages as dependencies

Update

paru -Syu

Version bumps land in the registry automatically:

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.
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

paru -Syu shows no update even though a new version was published: check the repo DB has the new version.

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:

paru -Syu --overwrite=/path/to/conflicting/file