Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-18 Thread Thomas Goirand
On 1/17/19 7:42 PM, Ben Finney wrote:
> Control: notfound -1 python3-httpretty/0.9.5-2
> Control: tags -1 - upstream
> Control: affects -1 - src:dput
> 
> On Fri, 2019-01-18 05:02 +11:00, Ben Finney  wrote:
>> Control: reassign -1 python3-httpretty
>> Control: found -1 python3-httpretty/0.9.5-2
>> Control: tags -1 + upstream
>> Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369
>> Control: affects -1 + src:dput

Hi,

I wonder what's the next course of action. Upstream has been known for
not being reactive at all. I'd bet on no reply before Buster freeze. Do
we really want dput to be removed from Debian?

Cheers,

Thomas Goirand (zigo)



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Ben Finney
Control: notfound -1 python3-httpretty/0.9.5-2
Control: tags -1 - upstream
Control: affects -1 - src:dput

On Fri, 2019-01-18 05:02 +11:00, Ben Finney  wrote:
> Control: reassign -1 python3-httpretty
> Control: found -1 python3-httpretty/0.9.5-2
> Control: tags -1 + upstream
> Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369
> Control: affects -1 + src:dput

-- 
 \
  `\
_o__) Ben Finney 



Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Debian Bug Tracking System
Processing control commands:

> notfound -1 python3-httpretty/0.9.5-2
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
The source python3-httpretty and version 0.9.5-2 do not appear to match any 
binary packages
No longer marked as found in versions python3-httpretty/0.9.5-2.
> tags -1 - upstream
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
Removed tag(s) upstream.
> affects -1 - src:dput
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
Removed indication that 910295 affects src:dput

-- 
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Ben Finney
Control: clone -1 -2
Control: retitle -1 dput: FTBFS: tests fail to mock HTTP request
Control: found -1 dput/1.0.2
Control: notforwarded -1
Control: summary -1 The HTTPretty library is failing to mock requests from 
Python's HTTPConnection.
Control: outlook -1 Either correct the HTTPretty library; or re-work the DPut 
test cases to avoid HTTPretty.
Control: block -1 by -2
Control: severity -2 important
Control: tags -2 - ftbfs

On Fri, 2019-01-18 05:02 +11:00, Ben Finney  wrote:
> Control: reassign -1 python3-httpretty
> Control: found -1 python3-httpretty/0.9.5-2
> Control: tags -1 + upstream
> Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369
> Control: affects -1 + src:dput

-- 
 \
  `\
_o__) Ben Finney 



Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #910295 [python3-httpretty] python3-httpretty: Fails to mock request sent 
with HTTPConnection
Bug 910295 cloned as bug 919599
> retitle -1 dput: FTBFS: tests fail to mock HTTP request
Bug #910295 [python3-httpretty] python3-httpretty: Fails to mock request sent 
with HTTPConnection
Changed Bug title to 'dput: FTBFS: tests fail to mock HTTP request' from 
'python3-httpretty: Fails to mock request sent with HTTPConnection'.
> found -1 dput/1.0.2
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
Marked as found in versions dput/1.0.2.
> notforwarded -1
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
Unset Bug forwarded-to-address
> summary -1 The HTTPretty library is failing to mock requests from Python's 
> HTTPConnection.
Summary recorded from message bug 910295 message 
> outlook -1 Either correct the HTTPretty library; or re-work the DPut test 
> cases to avoid HTTPretty.
Outlook recorded from message bug 910295 message 
> block -1 by -2
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
910295 was not blocked by any bugs.
910295 was not blocking any bugs.
Added blocking bug(s) of 910295: 919599
> severity -2 important
Bug #919599 [python3-httpretty] python3-httpretty: Fails to mock request sent 
with HTTPConnection
Severity set to 'important' from 'serious'
> tags -2 - ftbfs
Bug #919599 [python3-httpretty] python3-httpretty: Fails to mock request sent 
with HTTPConnection
Removed tag(s) ftbfs.

-- 
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
919599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Ben Finney
Control: retitle -1 python3-httpretty: Fails to mock request sent with 
HTTPConnection

On Fri, 2019-01-18 05:02 +11:00, Ben Finney  wrote:
> The HTTPretty library is failing to correctly mock requests sent using
> the standard-library `http.client.HTTPConnection` class.
> 
> I have registered a new bug report at the HTTPretty project bug
> tracker for this.

-- 
 \
  `\
_o__) Ben Finney 



Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 python3-httpretty: Fails to mock request sent with HTTPConnection
Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno 
-2] Name or service not known
Changed Bug title to 'python3-httpretty: Fails to mock request sent with 
HTTPConnection' from 'dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name 
or service not known'.

-- 
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Ben Finney
Control: reassign -1 python3-httpretty
Control: found -1 python3-httpretty/0.9.5-2
Control: tags -1 + upstream
Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369
Control: affects -1 + src:dput

On 16-Jan-2019, Ben Finney wrote:
> I suspect there's something changed with the ‘httpretty’ testing 
> library; either that, or something changed in recent Python 3 
> versions.

The HTTPretty library is failing to correctly mock requests sent using
the standard-library `http.client.HTTPConnection` class.

I have registered a new bug report at the HTTPretty project bug
tracker for this.

-- 
 \ “[F]reedom of speech does not entail freedom to have your ideas |
  `\accepted by governments and incorporated into law and policy.” |
_o__)   —Russell Blackford, 2010-03-06 |
Ben Finney 



Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-17 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 python3-httpretty
Bug #910295 [src:dput] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name 
or service not known
Bug reassigned from package 'src:dput' to 'python3-httpretty'.
No longer marked as found in versions dput/1.0.2.
Ignoring request to alter fixed versions of bug #910295 to the same values 
previously set
> found -1 python3-httpretty/0.9.5-2
Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno 
-2] Name or service not known
The source python3-httpretty and version 0.9.5-2 do not appear to match any 
binary packages
Marked as found in versions python3-httpretty/0.9.5-2.
> tags -1 + upstream
Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno 
-2] Name or service not known
Added tag(s) upstream.
> forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369
Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno 
-2] Name or service not known
Set Bug forwarded-to-address to 
'https://github.com/gabrielfalcao/HTTPretty/issues/369'.
> affects -1 + src:dput
Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno 
-2] Name or service not known
Added indication that 910295 affects src:dput

-- 
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-16 Thread Ben Finney
Control: tags -1 + confirmed

On 04-Oct-2018, Helmut Grohne wrote:

> At least the vast majority of failures is due to a similar 
> socket.gaierror.

I confirm that this behaviour is reproducible in a new SBuild chroot, 
created with ‘sbuild-debian-developer-setup’ (version “0.78.0-2”).

The behaviour is not specific to SBuild chroot though. It also occurs 
when running the test suite in a normal development environment.

I suspect there's something changed with the ‘httpretty’ testing 
library; either that, or something changed in recent Python 3 
versions.

-- 
 \ “A man must consider what a rich realm he abdicates when he |
  `\   becomes a conformist.” —Ralph Waldo Emerson |
_o__)  |
Ben Finney 



Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2019-01-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + confirmed
Bug #910295 [src:dput] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name 
or service not known
Added tag(s) confirmed.

-- 
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

2018-10-04 Thread Helmut Grohne
Source: dput
Version: 1.0.2
Severity: serious
Tags: ftbfs

dput fails to build from source with sbuild in unstable/amd64. A buil
log ends with:

| ==
| ERROR: test_request_has_expected_fields 
(test.test_methods.http_upload_SuccessTestCase)
| 
test.test_methods.http_upload_SuccessTestCase.test_request_has_expected_fields 
(file-list-three,size-100k,incoming-has-trailing-slash,https,username,chatter)
| --
| testtools.testresult.real._StringException: Traceback (most recent call last):
|   File "/<>/test/test_methods.py", line 1003, in 
test_request_has_expected_fields
| self.function_to_test(**self.test_args)
|   File "/<>/dput/methods/https.py", line 16, in upload
| progress, protocol="https")
|   File "/<>/dput/methods/http.py", line 138, in upload
| conn.endheaders()
|   File "/usr/lib/python3.6/http/client.py", line 1234, in endheaders
| self._send_output(message_body, encode_chunked=encode_chunked)
|   File "/usr/lib/python3.6/http/client.py", line 1026, in _send_output
| self.send(msg)
|   File "/usr/lib/python3.6/http/client.py", line 964, in send
| self.connect()
|   File "/usr/lib/python3.6/http/client.py", line 1392, in connect
| super().connect()
|   File "/usr/lib/python3.6/http/client.py", line 936, in connect
| (self.host,self.port), self.timeout, self.source_address)
|   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 617, in 
create_fake_connection
| s.connect(address)
|   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 404, in 
connect
| self.truesock.connect(self._address)
| socket.gaierror: [Errno -2] Name or service not known
| 
| 
| --
| Ran 4791 tests in 70.582s
| 
| FAILED (errors=192, skipped=115)
| Test failed: 
| error: Test failed: 
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
| dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
| make: *** [debian/rules:22: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

At least the vast majority of failures is due to a similar
socket.gaierror. Given that the chroot was created with
sbuild-createchroot, I'd expect that it should be "good enough". If that
isn't the case, we should fix sbuild. I've seen a discussion to make
netbase build-essential. Possibly that is related?

If you reassign the bug, make sure to "affects -1 + src:dput".

Helmut