On 2014-10-23, Petter Reinholdtsen wrote: > [Vagrant Cascadian] >> By the time ltsp-client-builder runs, apt should be configured in the >> installed system, and the http-proxy plugin should use the proxy >> configured in apt: >> >> /usr/share/ltsp/plugins/ltsp-build-client/Debian/010-http-proxy > > Right. But I guess it is running too late. :( ... > The wget call in the script > <URL: > https://anonscm.debian.org/cgit/debian-edu/debian-edu-config.git/tree/share/ltsp/plugins/ltsp-build-client/Debian-custom/000-arch-detection > > > got stuck because wget did not use the proxy set in d-i. I had to add > a timeout to avoid a endless hang.
I don't think this is appropriate to fix in ltsp-client-builder, as it
won't work when running outside of debian-installer.
I'd suggest fixing the above 000-arch-detection script to set the proxy
in the same way the http-proxy plugin is doing:
if [ -z "$http_proxy" ]; then
eval $(apt-config shell http_proxy acquire::http::proxy)
[ "$http_proxy" = "false" ] && http_proxy=""
export http_proxy
fi
The 000-arch-detection script you've referenced also abuses the
commandline processing internals ($option_*_value) which means you're
overriding the commandline options specified by the user, for what it's
worth.
live well,
vagrant
pgpw2mVVkEJkw.pgp
Description: PGP signature
