Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-16 Thread Sébastien Delafond
On Dec/15, Maximilian Hils wrote: > (2) mitmproxy may still be installable, but it potentially just > breaks due to backwards-incompatible changes within the dependency. > If I understand things correctly, there's no automated testing that > would alert someone in either case, so (2) may be

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-15 Thread Maximilian Hils
Hi Sébastien, > Ideally, your setup.py wouldn't include versioned dependencies That would mean that `pip install mitmproxy~=0.18` won't work in a year from now because one of our dependencies released a backwards-incompatible release in the meantime. From a Python/pip perspective, not specifying

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-15 Thread Sébastien Delafond
On Dec/14, Maximilian Hils wrote: > Upstream here. If there's anything we can do to make your life easier, > please let us know! > > We only list known compatible versions in setup.py as we'd like to > avoid running around with the fire extinguisher every time one of our > dependencies publishes

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-14 Thread Maximilian Hils
Upstream here. If there's anything we can do to make your life easier, please let us know! We only list known compatible versions in setup.py as we'd like to avoid running around with the fire extinguisher every time one of our dependencies publishes an backwards-incompatible release. We had too

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-14 Thread Sébastien Delafond
On Dec/13, Bob Proulx wrote: > Therefore I don't have a good idea of what to do here. I only know > that it is an impossible system. I feel certain this can't be > necessary. While I appreciate your concern, and am also pained by seeing so many versioned conflicts, what you *feel* is

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-13 Thread Bob Proulx
Sébastien Delafond wrote: > On Dec/03, Bob Proulx wrote: > > By my count there are 23 "<<" dependencies in use with mitmproxy! > > Wow! That is a lot of very fragile and breakage prone packages. It > > is doomed to have repeated breakages in Sid and Testing as those > > modules get uploaded. It

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-05 Thread Sébastien Delafond
On Dec/03, Bob Proulx wrote: > By my count there are 23 "<<" dependencies in use with mitmproxy! > Wow! That is a lot of very fragile and breakage prone packages. It > is doomed to have repeated breakages in Sid and Testing as those > modules get uploaded. It isn't a good way to do things.

Bug#846850: mitmproxy uninstallable in current Sid and soon Stretch Testing (again)

2016-12-03 Thread Bob Proulx
Package: mitmproxy Version: 0.18.2-3 Severity: important The dependencies for mitmproxy render it uninstallable in Sid today due to "Depends: python-passlib (<< 1.7)". But python-passlib 1.7.0-1 was uploaded to Sid on 2016-11-28. This is basically a deja-vu bug of Bug#844060 with a different