On Thu, Jun 04, 2026 at 11:50:18AM +0800, Otto Kekäläinen wrote:
Indeed deb.debian.org is hardcoded in this file:
src/container/enable-source-repositories.sh: deb
http://deb.debian.org/debian bullseye main
src/container/enable-source-repositories.sh: deb
http://deb.debian.org/debian-security bullseye-security main
src/container/enable-source-repositories.sh: deb
http://deb.debian.org/debian bullseye-updates main
src/container/enable-source-repositories.sh: URIs: http://deb.debian.org/debian
Also the container images most likely also have deb.debian.org
hardcoded inside them (as distributed by Debian and Ubuntu) and I am
not aware of any handy system to have them updated on the fly. Perhaps
have a local DNS that returns deb.debian.org as a local IP that has
the closes mirror?
I will leave this bug open for suggestions on how to nicely implement
automatic local mirror injection.
This is a standard problem for all of our build and build assistant
toold including QA. Most of them have a configuration file, support
auto-apt-proxy, or at least have a command line option to specify the
mirror to use.
Overriding a DNS record of debian.org is possible in my home network
(I'd still rather not do that), but this would, for example, not have
been possible during Minidebconf Hamburg.
Grüße
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
