openssl-1.0
Category: local-install (rebuilt only so archlinuxaba/the cluster gets it
too; not maintained/adapted/owned by us — see
arch/scripts/install_only_packages). Compat OpenSSL 1.0.2 build
(libssl.so.1.0.0/libcrypto.so.1.0.0, headers/binary under
openssl-1.0-namespaced paths) for software that still needs the old
ABI, e.g. python2 (see memory/python2.md).
Build notes (2026-08-19): extended to i686/pentium4
- Local checkout was byte-identical to the real upstream AUR PKGBUILD
(
diffagainstcgit/aur.git/plain/PKGBUILD?h=openssl-1.0showed no differences) but declaredarch=('x86_64')only, even thoughbuild()already had a workingi686branch (openssltarget='linux-elf') baked in by upstream itself – just never exposed viaarch=(). - Added
pentium4to the sameelifbranch asi686(same 32-bit x86 Configure target,linux-elf) and extendedarch=('x86_64' 'i686' 'pentium4'). Built and published cleanly on the first try, all three arches. check()’s OCSP test prints severalVerification: FAILED/=== INVALID SIGNATURE ... ===lines duringmake test– these are the test suite’s own expected-negative-result cases (intentionally malformed OCSP responses/certs), not real failures. Confirmed by all six packages (openssl-1.0+openssl-1.0-debugper arch) actually gettingUPLOADED; a realcheck()failure would have printed=== <arch> FAILED ===and skipped the upload.pkgrel7(upstream) ->7.1(local-install, X.Y scheme – the arch extension is a local deviation, not an upstream release).- Found and cleaned up stale untracked build artifacts (old
.pkg.tar.zst, downloaded tarball,pkg//src/dirs) left over from an earlier, apparently interrupted build attempt before this one – harmless, just noting in case a similar leftover shows up again.