Alpine's community/libqmi is at upstream 1c972b8a (2026-10-05), 23 commits
past the 30f3e998 this fork pinned "just past the !470 merge", with the
qmi-glib 1.39.1 the GNSS patches in modemmanager need. No patch was left;
the fork's one remaining addition, the FP6-tuned build (-march/-mtune,
whose gain was never measured), goes with it. build.sh loses its tarball,
checksum and build steps.
The registry still serves the fork (1.39.1_git20260808-r100 and -r101),
and that version outranks Alpine's 1.38.0_git* line, so with the aport
alone installed phones keep the fork and a fresh image takes it back at
its first 'apk upgrade': the fork's packages are deleted from the
registry with this push. Fresh images then install Alpine's libqmi and
keep it. Installed phones keep the fork until 'apk upgrade -a' downgrades
them to Alpine's or Alpine's version passes 1.39.1; the new modemmanager
works on either (verified on the FP6 with both).
pmbootstrap keeps a local package repository in its work dir and consults
it before every other repository. Whether that dir survives from one CI
run to the next is not established (run 60 rebuilt libqmi, modemmanager
and libcamera at the versions run 58 had built, which says it did not),
but nothing guarantees it either way, so build.sh deletes any
libqmi/qmi-utils apks found there before building, re-indexes the
repository from the files present and fails the run if any are left; the
publish step skips libqmi-*/qmi-utils-* as the backstop. pmbootstrap's
'zap --pkgs-local-mismatch' cannot do this: with systemd selected it looks
at packages/systemd-edge, not at the packages/edge the builds land in.
Jorijn van der Graaf
7157c54b10