@broder: take over all you want - I mostly agree with you and I don't think I have anything else to offer.
I agree squid-deb-proxy is at fault. I am not sure I agree that installing it should interfere with the install process. for instance, if the installer uses dhcp, but I configure the target with a static IP, I would not expect that IP get used until the install is finished and reboots into the new system. But this just in from #ubuntu-installer: (01:38:50 PM) cjwatson: CarlFK: the installer should rely on /target being functional. I think your previous bug is good enough, though; this is a one-off issue with squid-deb-proxy-client, and I don't think it's worth trying to solve generically - we'll just figure out how to deal with that issue My guess is that apt-avahi-discover should not return "http://:/"; ever; if it can't find a proxy for whatever reason, it should return "" and let the calling code figure out what to do. I also guess we are all in agreement on this. Getting the daemon to run so that a proxy is detected is up for debate. Personally I want the installer to keep using the on I specified, but I am not sure it would cause a problem if it didn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889656 Title: installer stops using proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/889656/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
