obexftp

• Path: arch/maintained/obexftp
• 2026-07-16: built and published, no PKGBUILD change needed (pkgrel stayed at 7). Was blocked purely by a dependency chain, not a defect of its own:
  • depends=('openobex' ...) — openobex itself was failing to build (see memory/openobex.md, fixed same day: missing docbook-xml/docbook-xsl makedepends). Once openobex was fixed and published, this resolved cleanly.
  • makedepends=(... 'python2' ...) — the already-published python2 package (in this project’s own archlinuxaba repo) itself depends on openssl-1.1, which had never been successfully published (own build failure: enable-ktls no longer a supported Configure option). The user published openssl-1.1 manually into archlinuxaba (2026-07-16, version 1.1.1.w-11) to unblock this — not fixed/built via this project’s own tooling.
  • Needed a pacman -Sy (stale local sync db) to actually see the freshly-published openssl-1.1 and python2 after publishing steps that just preceded it, even though pacman -Si immediately listed the repo it was in — worth remembering when a just-published dependency seems to still 404 in a build.
• Built with scripts/archlinuxaba-x86_64-build (needs the private repo in the chroot’s pacman.conf for python2/openssl-1.1 and, before that day, for the freshly-published openobex) — 0 compiler errors, obexftp and obexftp-debug produced, then signed+ published.

2026-10-19: rebuild attempt for perl 5.44 ABI bump FAILED – real SWIG/python2 regression, not fixed

Attempted a content-free rebuild (pkgrel 7 -> 7.1, x86_64 only) alongside [[cyrus-imapd2]]/[[perl-crypt-ssleay]]’s perl-5.44 rebuilds, since this package also ships a compiled perl XS module (OBEXFTP.so via -DENABLE_PERL=YES). The perl bindings built and linked fine against perl 5.44 – not a perl problem. But the overall build failed in the Python SWIG bindings (-DENABLE_PYTHON=YES -DPYTHON_EXECUTABLE=/usr/bin/python2 ..., PKGBUILD lines ~43-46):

clientPYTHON_wrap.c:1280:3: error: #error "This version of SWIG only supports Python >= 3.5"

Root cause: the installed swig (4.5.1-1) has dropped support for generating Python-2-compatible wrapper code – its generated clientPYTHON_wrap.c now unconditionally requires Python >= 3.5, but this PKGBUILD still targets python2/python2.7 throughout. This is a real, pre-existing latent incompatibility (not introduced by anything in this session) that only surfaced now because nothing had rebuilt this package since swig moved past the version that dropped py2 support – the currently-published obexftp-7 binary pre-dates this and is untouched/still fine.

Decision (user, 2026-10-19): leave it for now, don’t disable Python bindings or attempt a python2->python3 port yet. Reverted the pkgrel bump (back to plain 7, no rebuild happened, nothing published).

Future direction flagged by user: may need to fork/vendor an older swig release (the last one that still generates valid Python-2 wrapper code) as a separate local package (e.g. swig2 under adapted/ or similar), specifically to keep building this package’s Python bindings against python2, rather than porting the bindings to Python 3. Not started – just a direction to pursue next time this comes up. Check archive.org/SWIG’s own release history for the last pre-"Python >= 3.5 only” version before scoping that fork.