aurupdater

kirigami2

Build times (auto-updated)

Category: local-install. First publish 2026-09-21, 5.116.0-2.

Why this exists

maintained/plasma-framework5 has a hard depends=(... kirigami2), but kirigami2 (the KF5/Qt5 QtQuick components set) has been dropped entirely from the official extra repo – KDE’s ecosystem moved to KF6/Qt6 (extra/kirigami 6.30.0 is the Qt6 replacement, a different package). Discovered while investigating whether plasma-framework5 needs qt5-doc in makedepends (see [[plasma-framework5]]): a scratch test build could only resolve kirigami2 via a stale cached .pkg.tar.zst still sitting in this host’s pacman cache from before it was dropped – confirming plasma-framework5’s real-pipeline 5.116.0-2 publish depended on that same now-gone-from-extra package, undetected until this session.

Still available on the AUR (orphaned – Maintainer: null per AUR RPC – but FirstSubmitted == LastModified, i.e. submitted once by arojas and never touched again, sitting at exactly 5.116.0-2, the version plasma-framework5 needs). All of its deps (qt5-quickcontrols, qt5-quickcontrols2, qt5-graphicaleffects) and makedeps (extra-cmake-modules, qt5-svg, qt5-tools, kpackage5) are still in official extra – no further blockers.

Same validpgpkeys entry as kinit5/plasma-framework5 (53E6B47B45CEA3E0D5B7457758D0EE648A48B3BB, David Faure – expired 2021, but verifies fine with just a warning in this pipeline, see [[kinit5]]’s AUR-comment note).

Built and published cleanly on the first try, x86_64 only (matches upstream arch=(x86_64)). Now that this is published to archlinuxaba, plasma-framework5 rebuilds resolve kirigami2 from the real repo instead of depending on a stale host pacman-cache copy.

2026-09-27: adopted – now maintained/, not local-install/

The orphan AUR listing described above got adopted (a real submodule now exists at arch/maintained/kirigami2, origin pointed at ssh://aur@aur.archlinux.org/kirigami2.git, Maintainer: line in the PKGBUILD changed to us) – per project policy this is a manual, human-only step (see project_orphaned_category memory), done outside this session’s own visibility. Found the submodule already staged (git status showed Am maintained/kirigami2) with local PKGBUILD edits (pkgrel 2 -> 3) already made but an in-place build (run directly inside the tracked submodule dir, not via the normal /data/INSTALL staging path) that had been interrupted partway through compiling.

Cleaned up the stray untracked build byproducts left in the tracked submodule dir (source tarball + partial build log from that interrupted in-place attempt) and rebuilt properly via repo_release.sh maintained/kirigami2 (the normal staged path). Removed the now-redundant local-install/kirigami2 line from scripts/install_only_packages. Built + published clean, 5.116.0-3, x86_64 only. Same pre-existing namcap notes as before (LGPL not a strict SPDX identifier, several QML modules flagged as “uninstalled dependency” – false positives namcap can’t resolve for QML plugin packages, the consuming application provides those at runtime) – cosmetic, not addressed.