Dirk Müller píše v So 06. 04. 2019 v 11:41 -0500:
I would like to raise attention to the recent refactoring of python- python-subunit. the pypi name of that is still "python-subunit", and there are a number of things depending on the pypi name to be correct, so now again all of our python stack is completely unresolveable.
We were matching up what other distros do to track it from the main subunit package as they needed to be all shipped at once: https://tracker.debian.org/pkg/subunit https://src.fedoraproject.org/cgit/rpms/subunit.git/tree/
As otherwise the only workable version was 1.2.
you can check that this is correct here:
grep name= subunit-1.3.0/setup.py
this broke just recently with the drop of python-python-subunit from Factory, which however still existed in devel:languages:python, so we had a weird mixmatch of things.
so, I would like to understand why we were renaming the package away from a standard name to a one-off naming, and not even provide a compatibility provide to at least fix all the rpm unresolvables introduced by this. Is there some magic new policy that I'm not aware of? I wasn't able to spot a reason for taht in the changes file.
There are still the provides for python2-bla and python3-bla it seems we accidentally missed to provide also python-bla to keep it working on Leaps.
Also, since this broke all of the OpenStack CI and rendered about 700 packages completely unbuildable, I would have really liked to see this act of renaming discussed before it was simply done. Could we somehow try to coordinate such major things without pulling the rug under everyone else while they're travelling from/to susecon?
This was being processed for 5 months in staging projects for Tumbleweed. It is kinda weird no cloud integration checks spotted it.
Also I see you took upon yourself 'fixing' it over the weekend in the develprj where you messed it even more when you removed the patches and didn't add unittest2 dependency now.
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: