Connectivity issues on build.snapcraft.io

snapcraft
1

/build/75295e9a4b724f23ae1439964a8fc600-xenial/parts/tomcat/install/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/security/cacerts will be a dangling symlink
Pulling tomcat
svn: E170013: Unable to connect to a repository at URL ‘http://svn.apache.org/repos/asf/tomcat/tc8.5.x/trunk’
svn: E670002: Name or service not known

Any idea why it can’t connect to the SVN server??

Thanks

Tom

2

This looks like https://bugs.launchpad.net/snapcraft/+bug/1718245

3

Even though it works outside of build.snapcraft.io ?

4

Yes, the launchpad builders (which build.snapcraft.io uses) are behind a proxy … not sure where a solution to the issue stands though … perhaps @sergiusens can help out here since he commented on the bug too …

5

I can think of a workaround, but subversion provides no easy local way to determine the proxy, for which we haven’t had the handler take care of the setup as with other components.

Something like this might work:

parts:
    subversion-source:
        source: https://svn.apache.org/something/something
        plugin: autotools
        after: [subversion-proxy-setup]
    subversion-proxy-setup:
        plugin: nil
        build: |
            echo "http-proxy-host=my.proxy" > $HOME/.subversion
            echo "http-proxy-port=80" > $HOME/.subversion
            # Maybe also http-proxy-username=[username]
            # And #http-proxy-password=[password]

For which, it might be something buildd could just eventually end up setting up regardless of environment.

6

Thanks chaps, I’ll have a look.