As far as the original write-up goes, I can confirm that the problem I ran into with dnf was a C/C++ build system that directly created a system package for the system Python bindings, rather than emitting an sdist that could build fresh bindings for any Python installation.
Reworking the build system was more work than I was prepared to take on, so I instead reserved the name on PyPI and then allowed the use of system site packages in the project that needed those bindings.
The rpl package is waiting for being unblocked since October. Is there anything I can do to help unblock it?
As I feared, PyPI admin time is becoming a bottleneck now. I understand the reasons, but, wouldnât it be better to have a process that doesnât require admin access for the undisputed cases?
Yes that would be good, as long as @encukou investigates first to see if itâs legit the risk of releasing a package name to the wrong person should be minimal.