Thanks Seth. No apt-cacher-ng in the original failing setup, but I do have squid-deb-proxy in the container I used to test the reproducer. I have re-confirmed, both in the container and the original installer VM, that no apt proxy is required to produce this bug.
Thanks Seth. No apt-cacher-ng in the original failing setup, but I do have squid-deb-proxy in the container I used to test the reproducer. I have re-confirmed, both in the container and the original installer VM, that no apt proxy is required to produce this bug.