[Pkg-ltsp-devel] Bug#766460: ltsp-client-builder: Need to set web proxy environment in postinst

[Vagrant Cascadian]

On 2014-10-23, Petter Reinholdtsen wrote:
> On a machine behind a firewall enforcing the use of a web proxy, like
> the setup I have in my lap (simulating schools around the country), the
> LTSP plugin scripts are unable to use wget and similar tools to check
> what they can reach on the web.

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


> The fix is to add code similar to the one in base-installer, where
> http_proxy and https_proxy is passed on when set.

It doesn't currently have code for https_proxy, but it would be
reasonably easy to add. In the apt configuration, there's also
ftp_proxy, not sure if that's needed as well.


> Please add code similar to this in the ltsp-client-builder postinst:
>
>   load_proxy_conf() {
>     db_get mirror/protocol || true
>     local PROTOCOL="$RET"
>     if [ "$PROTOCOL" = "http" ]; then
>         db_get mirror/http/proxy
>         http_proxy="$RET" || true
>         if [ "$http_proxy" ]; then
>             export http_proxy

This is feasible to add, although I'd like to know why it isn't working
with the plugins already in place...


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20141023/50098275/attachment.sig>