[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-06 Thread Launchpad Bug Tracker
This bug was fixed in the package golang-github-go-resty-resty - 2.4.0-1ubuntu1 --- golang-github-go-resty-resty (2.4.0-1ubuntu1) impish; urgency=medium * d/rules: Override dh_auto_test and unset $http_proxy before invoking the target. (LP: #1942491) -- Sergio Durigan Junior

[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-03 Thread Sergio Durigan Junior
For the sake of completeness, I was able to determine the right place to unset the $http_proxy variable inside the project so that it also works. One should place an os.Unsetenv call as the first instruction of the following function: func dc() *Client which can be found inside the resty_test.go

[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-03 Thread Lucas Kanashiro
Thanks for the patch Sergio! As we discussed I believe this is a reasonable solution to unblock this package (might not be the ideal). The packaging changes look good, +1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.la

[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-03 Thread Sergio Durigan Junior
Thanks for the review, Lucas. Uploaded: $ dput golang-github-go-resty-resty_2.4.0-1ubuntu1_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /home/sergio/work/golang-github-go-resty-resty/golang-github-go-resty-resty_2.4.0-1ubuntu1_source.changes: Valid signa

[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-02 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942491 Title: autopkgtest failure (proxy-related) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu

[Bug 1942491] Re: autopkgtest failure (proxy-related)

2021-09-02 Thread Sergio Durigan Junior
So, after investigating this bug a bit, I was able to reproduce it locally (thanks to https://wiki.ubuntu.com/ProposedMigration#I.27m_seeing_a_squid_proxy.3F__My_tests_behave_differently_there.21), and was also able to confirm that when $http_proxy is unset, everything passes. My first attempt at