So it seems that this is indeed a runtime incompatibility - which
makes sense with mitmproxy binary having a versioned dependency on
python3-tornado (>= 4.3) right now. I think the best way forward would
be to update mitmproxy to 5.1.1, if we don't have enough confidence
that the outlined commit is
> Given that you say this was a build incompatibility, could you
> explain why you thought it was necessary to add a runtime Breaks:?
The setup.py for mitmproxy 4 sets an explicit upper limit on tornado
compatibility ("tornado>=4.3,<5.2"). The upstream commit [1] which relaxes
this constraint repl
2 matches
Mail list logo
