Autopkgtest failure with https_proxy or http_proxy set

[Olivier Gayot]

Autpkgtest is failing for libcloud when either http_proxy or https_proxy is set since the move to upstream version 3.4.1.

In the previous version (3.2.0-2), Debian applied a patch to disable some of the tests that are failing now.

test/test_connection.py seems to have code that handles HTTP proxies set when tests are executed, but is lacking code that would handle the HTTPS proxy.

test/test_http.py includes new tests which execute HTTP queries to the loopback interface. This can't work with proxies (unless the proxy is on the loopback interface).

test/compute/test_ovh.py is new and includes a test that requires access to the Internet.

[Olivier Gayot (ogayot)]

Added debdiff that applies multiple patches to:

1. fix closing sequence of the HTTP server in tests. This is not strictly necessary to fix the autopkgtest failures but other patches (i.e., see 2.) rely on the name of the function tearDownClass to be fixed (it used to be misspelled tearDownCls and code in there would be unreachable). Forwarded upstream and was merged yesterday.
2. handle http_proxy and https_proxy variables in various tests. Patches forwarded upstream (not merged currently)
3. disable the test that requires to be online (no need to uptream this one)

I will forward these patches to Debian (and update the dep3 headers accordingly) once I'm sure all autopkgtest failures are fixed.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "1-3.4.1-2__3.4.1-2ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Olivier Gayot (ogayot)]

Relevant patches have been merged upstream.

Forwarded the debdiff to Debian and also updated dep3 headers. Thanks.

[Lukas Märdian (slyon)]

Thank you @ogayot! You did a really good job here, adding all the relevant dep3 headers, submitting changes upstream, sending the delta back to Debian and connecting all the dots.

We also have a successful PPA build: https://launchpad.net/~ogayot/+archive/ubuntu/kinetic-proposed/+sourcepub/13610550/+listing-archive-extra
And a PPA autopkgtest: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ogayot-kinetic-proposed/kinetic/amd64/libc/libcloud/20220511_161623_60dac@/log.gz

Kudos! LGTM.

$ dput ubuntu ../libcloud_3.4.1-2ubuntu1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../libcloud_3.4.1-2ubuntu1_source.changes: Valid signature from BF7DB622B303AC8B
Checking signature on .dsc
gpg: ../libcloud_3.4.1-2ubuntu1.dsc: Valid signature from BF7DB622B303AC8B
Uploading to ubuntu (via sftp to upload.ubuntu.com):
  Uploading libcloud_3.4.1-2ubuntu1.dsc: done.
  Uploading libcloud_3.4.1-2ubuntu1.debian.tar.xz: done.
  Uploading libcloud_3.4.1-2ubuntu1_source.buildinfo: done.
  Uploading libcloud_3.4.1-2ubuntu1_source.changes: done.
Successfully uploaded packages.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libcloud - 3.4.1-2ubuntu2

---------------
libcloud (3.4.1-2ubuntu2) kinetic; urgency=medium

  * Fix autopkgtest failure on s390x (big-endian) (LP: #1973158)

 -- Olivier Gayot <email address hidden> Wed, 11 May 2022 15:51:43 +0200