On 2019-04-08, 10:11 GMT, you wrote:
Well that is for Matej to answer. I didn't control how the packages are named I didn't even notice the pypi name is python-subunit and not just subunit.
No, there is no renaming whatsoever. python-subunit project on PyPI (what was the upstream for our package python-python-subunit) was terminated as a project. So, we have completely replaced this package with new (mostly C++) package subunit, which also includes bindings (providing API compatibility) for many scripting languages, Python among them. So, python-python-subunit package should be completely eliminated by a subpackage from the subunit package (with the new upstream).
Also the python3-iso8601 is not broken, they just absolutely changed api between version 0.11 and 0.12 where no distribution apart from us ever shipped the 0.12 so you can fix it by downgrading:
0.12 is required by openstack, so I can't just downgrade it.
Do we know how complicated API we are talking about? How complicated it would be to patch subunit to work with the new API?
Best,
Matěj