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.
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.
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?