gtk2-ng-git

Build times (auto-updated)

• aarch64: 26m47s (2026-09-21 18:42 UTC, remote, MAKEFLAGS=-j1)
• x86_64: 13m5s (2026-09-21 18:16 UTC, MAKEFLAGS=-j6)

---

• Path: arch/maintained/gtk2-ng-git
• 2026-08-02: built+published cleanly (r22210.438b19a0d-1, + gtk2-ng-git-debug), x86_64. aarch64 skipped (no local extra-aarch64-build, expected). Nothing noteworthy.
• 2026-09-06: aarch64 remote build (eurobuild14) attempted twice as part of an ARM build-queue sweep – both times the background build task was killed externally right at the start (no error output, no build artifacts in /data/INSTALL/gtk2-ng-git beyond the raw synced source, nothing left running locally or on eurobuild14). Not reproduced for any other package in the same sweep (a2tools, check_ssl_cert, git-wd40, lockdev, oksh, shmux, xxdiff-git, bochs-gdb-stub, espeak all ran fine back-to-back). User confirmed they weren’t manually interrupting it and suspects a possible memory issue (host- or board-side, not narrowed down). Skipped for this session rather than retried a third time – aarch64 still not built/published for this package. Worth a fresh attempt next session, ideally with an eye on eurobuild14’s free memory right before/during the attempt.

AUR comment already resolved (checked 2026-09-21)

Samueru (2026-05-22) asked to add aarch64. Already done – arch= has included aarch64 since before this check, and it’s now actually published too (gtk2-ng-git-r22214.eb29a34fd-1-aarch64.pkg.tar.xz confirmed live on the remote repo – the earlier 2026-09-06 aarch64 build-kill issue above must have been resolved by a later successful rebuild). No action needed; no AUR reply posted (see [[python2]]’s 2026-09-21 entry for why).