packaging: drop the aport; fp6-img installs the published apk
All checks were successful
package / package (push) Successful in 1m55s

fp6-img no longer builds imsd from source: its images install the apk this
repo's package CI publishes to the registry (pinned version + sha256), so
the image and 'apk upgrade' carry the same binary and APKBUILD.binary is
the only imsd packaging left. The two payload files the aport carried
(kde-modem-daemon skel override, systemd preset) move up to packaging/,
where build-package.sh now takes them from.
This commit is contained in:
Jorijn van der Graaf 2026-09-02 16:08:21 +02:00
commit 1987275a54
6 changed files with 10 additions and 90 deletions

View file

@ -14,9 +14,10 @@ name: package
# Release gating is the version: pkgver comes from implementations/main.cpp,
# the registry answers 409 for an already-published version, and the publish
# step treats that as "nothing to do" — so pushes only release when the
# Version constant bumps. fp6-img images keep building imsd from their own
# pinned checkout of this repo (packaging/aport/); APKBUILD.binary's payload
# must stay identical to that aport's, so the two pipelines cannot skew.
# Version constant bumps. This is the only producer of the imsd apk: fp6-img
# images install the published package from the registry (pinned version,
# pinned sha256) instead of building their own, so image and 'apk upgrade'
# carry the same binary.
#
# Publishing needs PACKAGE_TOKEN (catbot account, package:write scope) — an
# org-level secret on Catcrafts since 2026-09-02, shared with fp6-img;