On 2026-05-25 14.18, Marc Haber wrote: > Package: autopkgtest > Version: 5.55 > Severity: normal > File: /usr/bin/autopkgtest-build-qemu > > I have auto-apt-proxy and that points to a working apt-cacher-ng:
[...] > However, building an image fails: > autopkgtest-build-qemu unstable ~/.cache/autopkgtest-qemu/unstable.img > Running /tmp/user/35300/tmplypzfddf/vmdb2-script using kvm backend > + export AUTOPKGTEST_APT_PROXY=http://10.0.2.2:3142 > + export AUTOPKGTEST_SETUP_APT_PROXY=http://127.0.0.1:3142 > + export http_proxy=http://127.0.0.1:3142 [...] > I: Target architecture can be executed > I: Retrieving InRelease > I: Retrieving Release > E: Failed getting release file > http://deb.debian.org/debian/dists/unstable/Release Hi Marc, I can't reproduce the problem. Before digging deeper, the first thing to check is the health of the data mirrored by your apt-cacher-ng. What I saw happening with apt-cacher-ng is that the cached Release file gets corrupted, and then apt operations fail in a way similar to what you described. In general I found apt-cacher-ng not very reliable, which is one reason why I resurrected squid-deb-proxy. Can you please purge all the data cached by apt-cacher-ng and try again? Thanks! Paride
