check_ssl_cert

Build times (auto-updated)

• armv7h: 1m20s (2026-09-29 05:00 UTC, remote, MAKEFLAGS=-j1)
• aarch64: 1m35s (2026-09-29 05:00 UTC, remote, MAKEFLAGS=-j1)
• armv6h: 2m24s (2026-09-29 05:00 UTC, remote, serial)
• i686: 1m28s (2026-09-29 04:56 UTC, MAKEFLAGS=-j6)
• pentium4: 1m35s (2026-09-29 04:57 UTC, MAKEFLAGS=-j6)
• x86_64: 50s (2026-09-29 05:47 UTC, MAKEFLAGS=-j6)

---

• Path: arch/maintained/check_ssl_cert
• Simple upstream-tarball package, no pkgver() function — .nvchecker.toml uses source = "git" against the upstream GitHub repo with prefix = "v" (tags are vX.Y.Z), so nvchecker’s reported version drops the v and matches pkgver directly.
• Update recipe is the standard one: bump pkgver, reset pkgrel to 1, updpkgsums (single md5sums entry, source is a GitHub release tarball), makepkg --printsrcinfo > .SRCINFO.
• Builds cleanly for x86_64, i686, pentium4 (its arch=() also lists armv6h/armv7h/aarch64 – see the 2026-09-29 entry below, these are now real too, not just declared).
• 2026-07-20: 2.101.0 -> 2.103.0, released to all three buildable archs.
• 2026-08-22: 2.103.0 -> 2.103.1, standard recipe, released to all three buildable archs (x86_64/i686/pentium4).

2026-09-29: 2.103.1 -> 2.103.3, first real build across all 6 archs

Only genuine UPD from a routine full check_for_updates_maintained.sh sweep this session. Standard recipe (bump pkgver, updpkgsums, regen .SRCINFO), no v2.103.2 tag exists upstream – jumped straight from .1 to .3. Cleaned a stale 2.103.1-1-armv6h leftover from 2026-09-12 in /data/INSTALL first.

armv6h/armv7h/aarch64 all built and published cleanly first try (the ARM cluster was up this session) – this package’s arch=() already listed them, and unlike gconf/gcc47/lacc-git/slimcc-git there was no dependency gap or codegen-target issue, just genuinely never had a version bump land while the cluster existed. i686/pentium4 also clean as always.

x86_64 hit a real infrastructure snag: the archlinuxaba-x86_64-build chroot’s base core/extra/multilib mirror (archlinux.lan.brgn.ch, a LAN mirror, distinct from archlinuxaba’s own dedicated archlinux32.andreasbaumann.cc server) was 404ing on extra.db specifically (core.db fetched fine) – confirmed via direct curl against the mirror’s real path (/archlinux/$repo/os/$arch, not the naive /​$repo/os/$arch guess tried first). Not transient – failed identically on a second attempt minutes later. Fixed (user-approved) by adding Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch as a fallback right after the broken line, in both /etc/pacman.d/mirrorlist (host) and /var/lib/archbuild/archlinuxaba-x86_64/root/etc/pacman.d/mirrorlist (the chroot’s own separate copy – not bind-mounted/live-synced from the host, so both needed the edit). x86_64 built clean on retry.

This LAN mirror gap likely affects every local x86_64 chroot build going forward until archlinux.lan.brgn.ch itself is fixed upstream – the fallback line should keep builds working regardless, but worth knowing this isn’t check_ssl_cert-specific if another package’s x86_64 build ever hits the same extra.db 404 (also relevant to i686/pentium4 chroots, which weren’t checked – they succeeded this run without needing the fallback, so may be pulling extra from a different/working mirror already, or just got lucky on cache).

All 6 archs published at 2.103.3-1 for the first time simultaneously.