> > The ci.debian.net results for mariadb seem to be very flaky lately (on > > amd64 they fail roughly 9/10) since version 1:10.11.6-1. Might be > > related (although the failure is different). i386 and arm64 seem to be > > exceptions. > > No - the current CI failures for MariaDB are unrelated and not due to > this local port issue. > > (Current MariaDB failures are partly due to OpenSSL API text change in > https://github.com/openssl/openssl/commit/81b741f68984 and partfly due > to upstream bug https://jira.mariadb.org/browse/MDEV-32843 - both > issues has known fixes, just a matter of dev time to commit and push)
New 1:10.116-2 uploaded with the two fixes above, looking good so far at https://tracker.debian.org/pkg/mariadb: autopkgtest for mariadb/1:10.11.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass The 'reserved port' issue has not been fixed, or at least I am not aware of any fix. However the issue was sporadic and I have not seen it in late 2023 or 2024 on any buildd or ci.debian.org log.
