kdstatemachineeditor
- Path: arch/adapted/kdstatemachineeditor
- Build failure during the 2026-07-07 “build all packages for x86_64”
private-repo release pass (see
repo_release_logs/adapted_kdstatemachineeditor.log).
arch=(any); makedepends/depends include qt5-declarative,
qt5-remoteobjects, qt5-scxml, graphviz. The clean extra-x86_64-build
chroot fails at dependency installation: error: target not found:
qt5-remoteobjects / qt5-scxml – these aren’t official Arch repo
packages, they’re other packages in this same arch/ tree
(maintained/qt5-remoteobjects, maintained/qt5-scxml), which the chroot
has no way to see unless they were already built and added to a local
pacman repo that the chroot syncs against.- This is a systemic gap, not specific to this package: the mass
build-everything pass processes packages in plain alphabetical order with
no dependency-graph awareness, and nothing feeds a package’s own build
output back into a local repo the chroot can install from mid-run. Any
package here that
depends/makedepends on another custom (non-official)
package from this tree will hit the same “target not found” failure,
regardless of build order, since chroots are always synced from the real
Arch mirrors + pacman.conf, not from anything built so far in this run.
See the new note added to memory/TOOLING_NOTES.md – expect this class
of failure to recur across the KDE5/Qt5 custom stack and similar
intra-tree dependency chains.
- Not fixed as part of this pass. A real fix would mean adding built
packages to a local repo (
repo-add + a [local] entry in the chroot’s
pacman.conf, refreshed via arch-nspawn/archbuild -r between builds)
so later builds in the same run can resolve earlier ones – out of scope
for a straightforward build+sign+publish sweep.