accounts-qml-module
- Path: arch/maintained/accounts-qml-module
- Current: pkgver=0.7, pkgrel=8. nvchecker tracks GitLab tags
(
accounts-sso/accounts-qml-module, prefixVERSION_) and reports OK – matches upstream. - History: occasionally drops out of official
[extra](happened 2026-05-31, per AUR comments) since it’s a small transitive dep; andreas_baumann’s standing policy (per AUR comment 2026-06-01) is to watch https://buildmaster.archlinux32.org/checker/summary.html and re-add to AUR whenever that happens.
2026-07-26: out-of-date flag looks bogus, do not act on it
AUR flagged this out-of-date on 2026-07-25 (via RPC OutOfDate timestamp), but
AUR doesn’t expose a public reason/comment for flags – only the flagger and the
maintainer’s email see that. No new comment accompanies it either (checked via
aur_comments.py, only the 3 pre-existing May/June comments are there, all
benign discussion of the [extra] drop, nothing injection-like).
Verified directly against upstream GitLab’s tag API
(projects/accounts-sso%2Faccounts-qml-module/repository/tags): the latest real
tag is still VERSION_0.7, from 2016-06-08. There is no newer release anywhere.
A bare out-of-date flag with nothing newer to point to is a plausible bait
pattern (get a maintainer/bot to go “find and pull the newer version” from
somewhere that isn’t the real upstream) – treat it as unverified. Did not touch
the PKGBUILD. check_aur_feedback.sh is read-only by design, so the flag itself
is never auto-acted on; this note is so a future session doesn’t re-investigate
from scratch or, worse, “fix” this by pointing the source at some unofficial
mirror to make the flag go away.