[PKG-Openstack-devel] Bug#755315: python-wsgi-intercept: FTBFS: Tests failures
David Suárez
david.sephirot at gmail.com
Sat Jul 19 18:48:38 UTC 2014
Source: python-wsgi-intercept
Version: 0.6.5-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> self = <urllib3.connectionpool.HTTPSConnectionPool object at 0x7f4e2d1e32e8>
>
> def _new_conn(self):
> """
> Return a fresh :class:`httplib.HTTPSConnection`.
> """
> self.num_connections += 1
> log.info("Starting new HTTPS connection (%d): %s"
> % (self.num_connections, self.host))
>
> if not self.ConnectionCls or self.ConnectionCls is DummyConnection:
> # Platform-specific: Python without ssl
> raise SSLError("Can't connect to HTTPS URL because the SSL "
> "module is not available.")
>
> actual_host = self.host
> actual_port = self.port
> if self.proxy is not None:
> actual_host = self.proxy.host
> actual_port = self.proxy.port
>
> conn = self.ConnectionCls(host=actual_host, port=actual_port,
> timeout=self.timeout.connect_timeout,
> > strict=self.strict, **self.conn_kw)
> E TypeError: __init__() got an unexpected keyword argument 'strict'
>
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:678: TypeError
> ===================== 2 failed, 20 passed in 0.57 seconds ======================
> E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build; python3.4 -m pytest
> dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/07/18/python-wsgi-intercept_0.6.5-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
More information about the Openstack-devel
mailing list