rootstock should understand http_proxy that uses mDNS for local host lookup during the build
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RootStock |
Fix Released
|
Medium
|
Ricardo Salveti | ||
Bug Description
This is against the rootstock 0.1.99.3 that comes with Ubuntu 10.04. Host is i386 building for a OMAP3 based Overo board.
I'm running apt-cacher-ng as a local package proxy. This runs on the host machine. The network is behind a ADSL gateway that acts as the DNS server. mDNS is used to provide the local host lookup. The host changes addresses depending on if it is hooked in over wireless or wired.
/etc/apt/
The HTTP proxy is set using 'export http_proxy=http://
The first stage runs fine and correctly uses the proxy. The second, qemu based stage fails due to not being able to resolve crucis.local. The build seems to complete fine. Using an IP address instead is fine.
I'd prefer to use the DNS name as this proxy setting is shared with the host itself when updating the host's version of ubuntu.
Related branches
| Michael Hope (michaelh1) wrote | #1 |
| summary: |
- Running apt-get against a proxy fails during the qemu stage + rootstock should add http_proxy DNS entries to /etc/hosts during build |
| Changed in project-rootstock: | |
| status: | New → Confirmed |
| assignee: | nobody → Oliver Grawert (ogra) |
| importance: | Undecided → Medium |
| Changed in project-rootstock: | |
| status: | Confirmed → In Progress |
| Ricardo Salveti (rsalveti) wrote | #2 |
| summary: |
- rootstock should add http_proxy DNS entries to /etc/hosts during build + rootstock should understand http_proxy that uses mDNS for local host + lookup during the build |
| Changed in project-rootstock: | |
| assignee: | Oliver Grawert (ogra) → Ricardo Salveti (rsalveti) |
| status: | In Progress → Fix Committed |
| Changed in project-rootstock: | |
| milestone: | none → 0.1.99.4 |
| status: | Fix Committed → Fix Released |
Fixed in revision 103.
I just changed the code to resolve the host name before using it inside the VM, for the second stage. Now it uses http_proxy when using debootstrap for the first stage, translate the ip of the host and use it for the second stage.
Note that the file /etc/apt/