Dear maintainer(s),

Your package has an autopkgtest, great. However, we're seeing failure on
some of the hosts of ci.d.n in the arch-all-support and
unsorted-packages-files tests. The output has a hint and indeed I
confirm on my amd64 laptop that I can reproduce it: with auto-apt-proxy
installed in the testbed (as done on hosts using a proxy) and when it
returns a value the tests fail.

/usr/bin/autopkgtest debootstrap --test-name unsorted-packages-files --
lxc --sudo elbrus

autopkgtest [09:19:58]: test unsorted-packages-files:
[-----------------------
  * Serving Flask app 'debian/tests/out-of-order-mitm.py'
  * Debug mode: off
WARNING: This is a development server. Do not use it in a production
deployment. Use a production WSGI server instead.
  * Running on http://127.0.0.1:5000
Press CTRL+C to quit
I: Using auto-detected proxy: http://10.0.3.1:3563
I: Retrieving InRelease
I: Retrieving Release
E: Failed getting release file
http://127.0.0.1:5000/debian/dists/testing/Release
autopkgtest [09:20:01]: test unsorted-packages-files:
-----------------------]

One possible solution I envision for the autopkgtest (untested) is to
run the test server on a port that's detected by auto-apt-proxy. Another
could be to remove proxy configuration in /etc/apt/apt.conf.d/ (i.e.
auto-apt-proxy.conf). But, quickly checking the test code, I wonder if
this is something that debootstrap should deal with (as in, if this is a
bug in debootstrap functionality).

Currently our loong64 and most of our riscv64 hosts use squid-deb-proxy
to provide a local cache.

Paul