Merge ~ahasenack/ubuntu/+source/node-configurable-http-proxy:kinetic-fix-build-1967024 into ubuntu/+source/node-configurable-http-proxy:ubuntu/devel
Status: | Merged |
---|---|
Merged at revision: | faafc2ac3a53054dce6a3a2385e298d4a1d4fcac |
Proposed branch: | ~ahasenack/ubuntu/+source/node-configurable-http-proxy:kinetic-fix-build-1967024 |
Merge into: | ubuntu/+source/node-configurable-http-proxy:ubuntu/devel |
Diff against target: |
39 lines (+11/-1) 3 files modified
debian/changelog (+6/-0) debian/control (+2/-1) debian/rules (+3/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergio Durigan Junior (community) | Approve | ||
Canonical Server | Pending | ||
Review via email: mp+420902@code.launchpad.net |
Description of the change
The build-time tests try to reach out to test.localhost.
$ host test.localhost.
test.localhost.
But launchpad builders use squid.internal as a proxy, and it will deny access to that domain, even though it returns 127.0.0.1.
The fix is to not use the proxy for that domain. A more thorough fix would also add that name to /etc/hosts, but we can't do that at build time.
I'm unsure if this is upstreamable to Debian, as they don't seem to have internet access restrictions. I can try, though, as it shouldn't break their build.
Sorry, no PPA because they are clogged up.
To test, I suggest:
- jammy build container
- another container running squid (sudo apt install squid, no config tweak needed)
- in the jammy build container, edit /etc/environment and set (replace "j-proxy.lxd:3128" with your proxy)
http_proxy=http://
https_proxy=http://
HTTP_PROXY=http://
HTTPS_PROXY=http://
no_proxy=
NO_PROXY=
- build this package in the jammy build container, while tailing /var/log/squid/*log in the squid container
You will see it trying to reach out to that test domain:
1651257039.836 0 10.0.100.6 TCP_DENIED/403 3890 GET http://
1651257039.893 0 10.0.100.6 TCP_DENIED/403 3858 GET http://
1651257039.896 0 10.0.100.6 TCP_DENIED/403 3890 GET http://
1651257039.901 0 10.0.100.6 TCP_DENIED/403 3858 GET http://
1651257039.903 0 10.0.100.6 TCP_DENIED/403 3890 GET http://
1651257039.941 0 10.0.100.6 TCP_DENIED/403 3875 GET http://
With the fixed package, there should be no build-related hits on the proxy, and the build should succeed. You might see snaps trying to update themselves, though ;)
Ah, Bryce's link to a debian build is from reproducible builds, not the debian builders:
https:/ /tests. reproducible- builds. org/debian/ rb-pkg/ unstable/ amd64/node- configurable- http-proxy. html
So they might take this. I'll submit.