svn source-type not honoring proxies

Bug #1718245 reported by Kevin W Monroe on 2017-09-19
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snapcraft
Medium
Unassigned

Bug Description

I attempted to build a snap on the launchpad builders that used 'source-type: svn'. These builders are behind an authenticated proxy, and it appears svn doesn't like that. Here you can see my snapcraft.yaml part and subsequent build failure:

http://paste.ubuntu.com/25565855/

The full build log is available here:

https://launchpadlibrarian.net/337431579/buildlog_snap_ubuntu_xenial_amd64_pig_BUILDING.txt.gz

I was able to work around this because my source happens to have a git mirror, and git works fine with launchpad builders. I believe the svn source handler needs to include proxy info (if present) in ~/.subversion/servers, as suggested by this SO answer:

https://stackoverflow.com/questions/1491180/how-to-configure-a-http-proxy-for-svn

Sergio Schvezov (sergiusens) wrote :

This is an invasive change to execute on a host as it would affect any existing configuration you have, that said, if executing in a container we can certainly try and get this going.

Changed in snapcraft:
status: New → Triaged
importance: Undecided → Medium
Neil McPhail (njmcphail) wrote :

There's a comment on that stackoverflow thread that current versions of Subversion honour the http_proxy environment variable. Could that be set a build time on the build server?

Colin Watson (cjwatson) wrote :

As far as Launchpad goes, this needs to be done in launchpad-buildd, and it's already filed there as bug 1668358. I guess it may still be worthwhile to keep this bug open separately for the case of running "snapcraft cleanbuild" in an environment that requires a proxy.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers