Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

2020-04-10 Thread Colin Watson
Control: reassign -1 python-wsgi-intercept 1.8.1-2 Control: clone -1 -2 Control: reassign -2 python3-httplib2 0.14.0-1 Control: retitle -2 python3-httplib2 >= 1.13.0 breaks python3-wsgi-intercept << 1.9.0 Control: block -2 by -1 On Tue, Feb 11, 2020 at 11:43:03PM +0100, Andreas Beckmann wrote: >

Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

2020-02-11 Thread Andreas Beckmann
Control: affects -1 + src:python-wsgi-intercept On 11/02/2020 12.45, Håvard Flaget Aasen wrote: > Since you marked it as found after my reply, does it mean that you want > it to be fixed in this (python-httplib2) package? > > How can it be found in a python2 package when python-wsgi-intercept

Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

2020-02-11 Thread Håvard Flaget Aasen
Since you marked it as found after my reply, does it mean that you want it to be fixed in this (python-httplib2) package? How can it be found in a python2 package when python-wsgi-intercept only builds for python3? Thanks, Håvard

Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

2020-02-10 Thread Håvard Flaget Aasen
According to [1] and [2] this issue was fixed in package wsgi-intercept version 1.9.0 Though they write that the change was indeed in the httplib2 package. I have not tested the new release of wsgi-intercept myself. Håvard [1] https://github.com/cdent/wsgi-intercept/issues/57 [2]

Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

2020-02-10 Thread Thomas Goirand
Hi, It looks like this bug is on httplib2. Indeed, it is the only place where I can read "tls_maximum_version", which is the "unexpected keyword argument" (this is *not* in wsgi-intercept). I'm therefore I'm reassigning the bug. Cheers, Thomas Goirand (zigo)