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 dependency.
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. Basically there are 23 timebomb snags in this package that can go off at any time due to any of those being upgraded. That is bad. Why so many timebombs in this package? Bob -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mitmproxy depends on: ii python-backports.ssl-match-hostname 3.5.0.1-1 ii python-blinker 1.3.dfsg2-1 ii python-brotli 0.5.2+dfsg-1 ii python-certifi 2016.2.28-1 ii python-click 6.6-1 ii python-configargparse 0.11.0-1 ii python-construct 2.5.2-0.1 ii python-cryptography 1.5.3-1 ii python-cssutils 1.0-4.1 ii python-flask 0.11.1-1 ii python-h2 2.4.1-1 ii python-hpack 2.3.0-1 ii python-html2text 2016.9.19-1 ii python-hyperframe 3.2.0-2 ii python-jsbeautifier 1.6.4-2 ii python-lxml 3.6.4-1 ii python-openssl 16.2.0-1 ii python-passlib 1.6.5-4 ii python-pil 3.4.2-1 ii python-pyasn1 0.1.9-2 ii python-pyparsing 2.1.10+dfsg1-1 ii python-pyperclip 1.5.27-2 ii python-requests 2.11.1-1 ii python-six 1.10.0-3 ii python-tornado 4.4.2-1 ii python-typing 3.5.2.2-1 ii python-urwid 1.3.1-2+b1 ii python-watchdog 0.8.3-2 pn python:any <none> Versions of packages mitmproxy recommends: ii python-pyperclip 1.5.27-2 mitmproxy suggests no packages. -- no debconf information
