Merge lp:~tribaal/launchpad-buildd/apt-proxy-injection into lp:launchpad-buildd
Proposed by
Chris Glass
Status: | Merged |
---|---|
Merged at revision: | 323 |
Proposed branch: | lp:~tribaal/launchpad-buildd/apt-proxy-injection |
Merge into: | lp:launchpad-buildd |
Diff against target: |
86 lines (+50/-0) 3 files modified
debian/changelog (+6/-0) lpbuildd/target/build_livefs.py (+10/-0) lpbuildd/target/tests/test_build_livefs.py (+34/-0) |
To merge this branch: | bzr merge lp:~tribaal/launchpad-buildd/apt-proxy-injection |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+335742@code.launchpad.net |
Description of the change
This branch adds a "--apt-http-proxy" option to the buildlivefs command, injecting the http proxy it specifies into the chroot (by setting the appropriate env).
This allows speeding up local development of cloud images (for example) significantly by setting up a squid-deb-proxy or similar.
To post a comment you must log in.
Please can you add a test for this? It should be possible to test the new behaviour in lpbuildd/ target/ tests/test_ build_livefs. py.
Aside from the code review comments below, this is probably fine as far as it goes. However, I'd suggest some follow-up work (which could be in a separate branch).
One of my usual local tweaks to launchpad-buildd is to add this to the end of lpbuildd. target. apt.OverrideSou rcesList. run:
This isn't totally satisfactory for various reasons, but it's been good enough as a local hack.
Now, if we were to polish this up, the most convenient approach would be if there were an item in the buildd's configuration file that gave a proxy URL. lpbuildd. debian. DebianBuildMana ger.doSourcesLi st could turn this into an option passed to override- sources- list, which could then inject an apt.conf.d file if that option is set. If we did that, it would make sense for lpbuildd.livefs to look at that same configuration item and pass the --apt-http-proxy option to buildlivefs too (which as it stands you're presumably having to do manually).