Comment 11 for bug 1753340

It's there any ETA on the proposal landing?

On Sun., 13 May 2018, 7:01 pm Colin Watson, <email address hidden> wrote:

> I'm not sure there is necessarily any way to get your build working
> before my proposal is landed. I mean, if we knew how to stuff the
> necessary information into ant in a way that causes it to work then we
> could just do it in snapcraft, right?
>
> Your assumption about needing four environment variables for each
> protocol is incorrect, perhaps because you misunderstood the Python
> code. http_proxy and https_proxy are each in this kind of form:
>
> http://USERNAME:PASSWORD@HOST:PORT/
>
> The snapcraft code that you pointed to in comment #3 unpacks this into
> host/port/username/password components and attempts to pass those on to
> ant in separate -D options. It's just that it doesn't appear to
> actually work ...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1753340
>
> Title:
> build failing on download by ant build
>
> Status in launchpad-buildd:
> Incomplete
>
> Bug description:
> I have a snap part which builds fine under lxd however it fails to
> build on the build servers.
>
> The error appears to indicate that it is unable to download a file
> which stops the build proceeding.
>
> There also appears to be an secondary error as there is an error
> regarding a python library however the snap in question doesn't use
> python for the build. The build uses ant so I'm guessing the python
> error might be caused by the python plugin for ant.
>
> The problem seems a little similar to a number of other reports
> related to ant in that there are some problems with ant downloading
> files.
>
> The difference with this issue is that it reports an error saying it
> can't find a file rather than that it can't download a file.
>
> For reference:
> https://bugs.launchpad.net/launchpad-buildd/+bug/1690834
> https://bugs.launchpad.net/launchpad-buildd/+bug/1702130
>
> https://code.launchpad.net/~cjwatson/launchpad-buildd/local-snap-proxy/+merge/322545
>
>
> The build in question is here:
>
> https://build.snapcraft.io/user/bsutton/tomcat-with-ssl-snap/158974
>
> The primary error is:
>
> testexist:
> [echo] Testing for
> /root/tomcat-build-libs/commons-daemon-1.1.0/commons-daemon-1.1.0.jar
> downloadgz-2:
> [mkdir] Created dir: /root/tomcat-build-libs
> setproxy:
> trydownload.check:
> trydownload:
> setproxy:
> trydownload.check:
> trydownload:
> BUILD FAILED
>
> /build/e4039a0b32e4bca67d290294684c86d6-xenial/parts/tomcat-with-ssl/build/build.xml:2623:
> The following error occurred while executing this line:
>
> /build/e4039a0b32e4bca67d290294684c86d6-xenial/parts/tomcat-with-ssl/build/build.xml:2773:
> the archive download-604074008.tar.gz doesn't exist
>
>
> Secondary error:
> Total time: 0 seconds
> ant
> /usr/lib/python3/dist-packages/ndg/httpsclient/subj_alt_name.py:22:
> UserWarning: Error importing pyasn1, subjectAltName check for SSL peer
> verification will be disabled. Import error is: No module named 'pyasn1'
> warnings.warn(import_error_msg)
>
> /usr/lib/python3/dist-packages/ndg/httpsclient/ssl_peer_verification.py:25:
> UserWarning: SubjectAltName support is disabled - check pyasn1 package
> installation to enable
> warnings.warn(SUBJ_ALT_NAME_SUPPORT_MSG)
> /usr/lib/python3/dist-packages/ndg/httpsclient/subj_alt_name.py:22:
> UserWarning: Error importing pyasn1, subjectAltName check for SSL peer
> verification will be disabled. Import error is: No module named 'pyasn1'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/launchpad-buildd/+bug/1753340/+subscriptions
>