Package: debci
Version: 3.11
Severity: normal
X-Debbugs-Cc: debian-ri...@lists.debian.org, invernom...@paranoici.org
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello Debian CI team!

I [uploaded] a new version of package 'apt-listbugs' to unstable and
noticed that the continuous intergration autopkgtests [fail] on riscv64.

[uploaded]: 
<https://tracker.debian.org/news/1621049/accepted-apt-listbugs-0146-source-into-unstable/>
[fail]: 
<https://ci.debian.net/packages/a/apt-listbugs/testing/riscv64/58295273/>

I cannot understand why. The same tests on other architectures seem to
succeed. And I also checked locally (with a qemu amd64 testbed), before
uploading, without experiencing any issue.

It seems that the tests that need Internet access (and are marked as
"needs-internet" in 'debian/tests/control') fail with the following error:

  302s /usr/bin/auto-apt-proxy: 176: avahi-browse: not found
  303s E: Failed to open TCP connection to :80 (Connection refused - connect(2) 
for "" port 80)
  303s E: Exiting with error

It should be noted that apt-listbugs will attempt to run an auto proxy
detect command, if one is found in APT configuration
( acquire::http::proxy-auto-detect ).
I guess the testbed has 'auto-apt-proxy' installed, but is it working
correctly?

Is there anything wrong in the tests defined in package 'apt-listbugs'?

Is there anything that fails to work in the riscv64 Debian CI testbed?

Is there anything that needs to be fixed anywhere else?

Please help me.
Thanks for your time and dedication!

Reply via email to