The builds of the xrootd-s3-http package for hurd-amd64 fail on some
buildds. At least hurd-dbdd-tls-1 is affected.

https://buildd.debian.org/status/logs.php?pkg=xrootd-s3-http&arch=hurd-amd64

The build fails because the tests fail. The build succeeds on hurd-i386
and on the exodar porterbox, so there doesn't seem to be any remaining
hurd specific issues in the code or the tests.

In the log of the failing builds the folloing lines can be seen:

=========================================
CLIENT LOG:
=========================================
* Uses proxy env variable https_proxy ==
'http://apt-proxy.tls.msk.ru:3142/'
* Host apt-proxy.tls.msk.ru:3142 was resolved.
* IPv6: (none)
* IPv4: 192.168.177.226
*   Trying 192.168.177.226:3142...
* CONNECT: no ALPN negotiated
* Establishing HTTP proxy tunnel to localhost:60084
* The requested URL returned error: 403

I.e. the client part of the test (running on localhost) tries to
contact the server part of the test (also running on localhist) via an
HTTP proxy tunnel on an external connection which obviously fails since
there is no external network on the buildds during the build.

The https_proxy environment variable should not be defined in the build
environment on the buildds.

The last build for hurd-amd64 that happened on a different buildd
(boralus) succedded, so the problem seem host specific.

Mattias

Hello,

Mattias Ellert, le lun. 19 oct. 2026 11:32:00 +0200, a ecrit:

Ah, yes, that was meant to make use of the proxy of the local network,
for apt use etc. In the meanwhile I added the use of
Acquire::HTTP::Proxy but forgot to remove the variable.

I have now removed the variable.

Thanks for the notice,
Samuel