PyGObject >= 3.52 dropped the standalone gobject-introspection
girepository-1.0 dependency and now builds against girepository-2.0,
which was merged into GLib 2.80. The linux extra pins PyGObject>=3.46
with no upper bound, so pip resolves the newest release (3.56.3) and
meson aborts metadata generation with:
Dependency 'girepository-2.0' is required but not found.
because CI only installed the old libgirepository1.0-dev.
Swap libgirepository1.0-dev -> libgirepository-2.0-dev (shipped by
GLib 2.80 on the ubuntu-latest / 24.04 runner) across all three Linux
pip-install paths so they stay in sync:
- test.yml: the failing linux-smoke job.
- release.yml: build-linux, which would otherwise ship a broken
Linux tarball on the next tag.
- build.yml: build-linux had no system-deps step at all; added the
matching apt install so the manual artifact build works too.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
workflow_dispatch-triggered build.yml that produces Windows
installer/portable and Linux tarball as CI artifacts without
creating a release. Trigger from Gitea UI → Actions → Run.
alexei.dolgolyov