http_proxy propagation

[Fabrizio Balliano]

when chroot-ing to remaster-root directory, we should propagate the "*_proxy" environment variables, doing that will allow users behind proxied to have a working uck, otherwise the build will fail

[Fabrizio Balliano (fabrizio-balliano)]

proxy variable read the right way, the problem is that apt-get update fail due to some proxy errors, maybe i'll do change when we do

apt-get update

with

(apt-get update || apt-get update)

so proxy lacks are always fixed in my case, i know, it's not uck bugs

[Fabrizio Balliano (fabrizio-balliano)]

released a small fix which re-execute apt-get update a second time if the first fails

[Stanislav German-Evtushenko (giner)]

proxy doesn't work for lucid

Steps to reproduce:
1. Boot Ubuntu 10.04 LiveCD
2. Configure proxy (apply to system-wide)
3. Install UCK.
4. Start to remaster ISO
5. Result: package information isn't got from the repository.

[Wolf Geldmacher (wolf-womaro)]

The problem seems to be the use of sudo/gksudo by UCK:

The *sudo commands by default reset the envrionment to a well defined
minimal set that does not include the proxy configuration.

If you add the following line:
Defaults env_keep += "http_proxy https_proxy ftp_proxy all_proxy no_proxy"
to the /etc/sudoers file, proxies should work for UCK (chroot) as well.

I'm not sure whether this solution should be implemented within the uck
package - I personally do not like packages messing around with my
sudoers configuration...

[Wolf Geldmacher (wolf-womaro)]

Found a way to handle this: uck-gui now saves the _proxy variables to $SCRIPT_DIR/environment where they can be picked up by the chrooted customize script, thus sudo does no longer have to pass them.

Seems to work fine and is part of the changes for UCK 2.4.4