Bug#906976: mitmproxy: FTBFS in buster/sid

2018-08-22 Thread Santiago Vila 
Package: src:mitmproxy
Version: 4.0.4-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
cat: debian/mitmproxy.manpages: No such file or directory
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy
copying mitmproxy/connections.py -> 
/<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy
copying mitmproxy/websocket.py -> 
/<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy

[... snipped ...]


def test_verification_w_confdir(self, tdata):
self.options.update(
ssl_insecure=False,
ssl_verify_upstream_trusted_confdir=tdata.path(
"mitmproxy/data/servercert/"
),
ssl_verify_upstream_trusted_ca=None,
)
>   assert self._request().status_code == 242
E   assert 502 == 242
E+  where 502 = Response(502 Bad Gateway, text/html, 
307b).status_code
E+where Response(502 Bad Gateway, text/html, 307b) = 
>()
E+  where > = 
._request

test/mitmproxy/proxy/test_server.py:320: AssertionError
_ 
TestHTTPSUpstreamServerVerificationWTrustedCert.test_verification_w_pemfile 
__

self = 

tdata = 

def test_verification_w_pemfile(self, tdata):
self.options.update(
ssl_insecure=False,
ssl_verify_upstream_trusted_confdir=None,
ssl_verify_upstream_trusted_ca=tdata.path(
"mitmproxy/data/servercert/trusted-root.pem"
),
)
>   assert self._request().status_code == 242
E   assert 502 == 242
E+  where 502 = Response(502 Bad Gateway, text/html, 
307b).status_code
E+where Response(502 Bad Gateway, text/html, 307b) = 
>()
E+  where > = 
._request

test/mitmproxy/proxy/test_server.py:330: AssertionError
=== warnings summary 
===
.pybuild/cpython3_3.6_mitmproxy/build/test/mitmproxy/tools/console/test_master.py::TestMaster::()::test_basic
  /usr/lib/python3/dist-packages/_pytest/python.py:195: RuntimeWarning: 
coroutine 'TestMaster.test_basic' was never awaited
testfunction(**testargs)

-- Docs: http://doc.pytest.org/en/latest/warnings.html
== 5 failed, 805 passed, 545 deselected, 1 warnings in 43.08 
seconds ===
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_mitmproxy/build; python3.6 -m pytest 
"-k-TestHARDump -k-TestScripts -k-test_mitmweb -k-test_mitmdump"
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:11: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mitmproxy.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906976: mitmproxy: FTBFS in buster/sid

2018-08-22 Thread Sébastien Delafond 
Control: retitle -1 FTBFS in buster
Control: tags -1 - sid + buster
thanks

In sid it builds fine during the 1st run, as shown here:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mitmproxy.html

The 2nd reproducible run fails because of the "date in the future"
thing: since the unit tests use a live example.mitmproxy.org host, there
are certificate issues when simulating a 09/2019 date.

However, your FTBFS in buster is not caused by that, as confirmed here:

  
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/mitmproxy.html

Something in the dependencies must be causing this error; I'll look into
it.

Cheers,

--Seb