kchmviewer

• Path: arch/maintained/kchmviewer
• Build failure during the 2026-07-07 “build all packages for x86_64” private-repo release pass (see repo_release_logs/maintained_kchmviewer.log).
• Needs qt5-webengine, not found anywhere in this arch/ tree (chmlib/libzip, also listed missing in the same transaction, are presumably real and would resolve fine on their own). Same external-dependency-not-in-this-tree class as memory/dbmodel-qt4.md – per the user’s 2026-07-07 guidance, recording and moving on rather than digging into whether it’s official-vs-AUR right now.
• Not fixed as part of this pass.
• 2026-07-30: retried – user had published qt5-webengine to archlinuxaba, chmlib/libzip resolve fine from official extra as expected, but the build still failed: qt5-webengine itself depends on qt5-webchannel, which is not in archlinuxaba (error: cannot resolve "qt5-webchannel", a dependency of "qt5-webengine"). So qt5-webengine’s own dependency chain is incomplete in the private repo, not something wrong with kchmviewer’s PKGBUILD. Needs qt5-webchannel published to archlinuxaba too before retrying.
• 2026-07-30, same day: user published qt5-webchannel too. Retried and built/published kchmviewer-8.0-8-x86_64 cleanly, no PKGBUILD changes needed.
• 2026-10-03: check_aur_feedback.sh reported REOPENED (“new comment since your reply”) – investigated and it was a false positive, a transient DNS failure during that run’s comment-page fetch, not a real new AUR comment. No action needed on this package; the newest AUR comment is still the maintainer’s own 2026-04-09 17:45 reply. See memory/TOOLING_NOTES.md’s 2026-10-03 entry for the script fix and state-file repair.