Source: construct Version: 2.8.16-0.1 Severity: grave Dear Maintainer (or non-maintainer, as it seems),
I just noticed that you recently re-uploaded construct/2.8.16-0.1 to unstable, without checking reverse dependencies. We had reverted to a 2.5-series version in February because the API had been broken (#853082) and the current upstream maintainers actively refused to do anything about it[1]. Nowadays, upstream even has an explicit notice about the API incompatibilities in their README.md[2]. So, what did you break? ,---- | $ apt-cache rdepends python-construct | python-construct | Reverse Depends: | python-dfvfs | mitmproxy | bdfproxy | plaso | python-ironic-inspector `---- The plaso and dfvfs packages are maintained by me and are affected by the API breakage. It looks like mitmproxy and bdfproxy are also affected. Only the latest version of ironic-inspector seems to depend on construct >= 2.8. I think I am going to package construct-legacy, based upon <https://pypi.python.org/pypi/construct-legacy>. Cheers, -Hilko [1] https://github.com/construct/construct/issues/271 [2] https://github.com/construct/construct#sticky
