adtpro-git

Build times (auto-updated)

• x86_64: 1h50m (2026-10-06 12:38 UTC, MAKEFLAGS=-j6)

---

• Path: arch/maintained/adtpro-git
• Initial build failure during the 2026-07-07 “build all packages for x86_64” private-repo release pass (see repo_release_logs/maintained_adtpro-git.log): source=() uses a git+... VCS source but makedepends (line 12, was ('cc65')) didn’t include git. ERROR: Cannot find the git package needed to handle git sources.
• Fixed 2026-07-07 later same day: added git to makedepends (makedepends=('cc65' 'git')), bumped pkgrel 1 -> 2 (packaging-only fix, no upstream change, so pkgrel not pkgver), regenerated .SRCINFO.
• Retried and got past the git error, but hit a different, genuine problem next: error: target not found: cc65. Unlike the KDE5/Qt5 stack (custom packages missing from a clean chroot but present in this tree), cc65 isn’t vendored anywhere in arch/ at all – it’s a real AUR-only package in actual Arch too, and this PKGBUILD apparently assumes it’s already installed on whatever system builds it (e.g. via a normal AUR helper outside this private-repo tooling), which a clean extra-x86_64-build chroot never has.
• Not fixed further as part of this pass – would need either vendoring a cc65 package into this tree, or building adtpro-git some other way that has cc65 available (e.g. pre-seeding the chroot, out of scope for a plain build+sign+publish run).
• 2026-08-02: vendored cc65 into the tree (see memory/cc65.md), which resolved the cc65 blocker. Hit one more: build() runs ant all but ant wasn’t in makedepends – ant: command not found. Fixed: added ant to makedepends (it pulls in java-environment/a JDK itself as its own dependency, so nothing else needed), pkgrel 1 -> 2. Built+published cleanly afterward (2.1.0.r17.g3580637-2), x86_64 only.

ant/JDK provider mismatch (found 2026-10-05, NOT fixed – needs a decision)

Rebuild during a full -git batch pass failed in build() (ant all):

java.lang.NoClassDefFoundError: .../ExitStatusException
Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.ExitStatusException

ant (extra, 1.10.17-1) depends on the virtual package java-environment, which is ambiguous in this tree: besides the normal OpenJDK providers in extra (jdk-openjdk/11/17/21/25), our own archlinuxaba/jdk10 ([[jdk10]], Oracle JDK 10, EOL) also provides java-environment=10 (versioned provide). The clean chroot picked jdk10 (log: “JDK 10 set as default Java environment”), and modern Ant 1.10.17’s launcher then fails to classload its own ExitStatusException under that ancient JVM – version mismatch between current Ant and jdk10, not an adtpro-specific bug.

Likely fix: add a concrete modern JDK (e.g. jdk21-openjdk) to adtpro-git’s own makedepends, ahead of ant, so java-environment is already satisfied by the time ant installs and the ambiguous provider resolution never happens. Packaging-only, would be pkgrel 2 -> 3. Not applied – counts as a non-routine PKGBUILD change ([[feedback_ask_before_nonroutine_pkgbuild_changes]]), left for the user to confirm. Worth checking whether any other ant-dependent package in this tree hits the same jdk10 tie-break.