On Wed, Oct 08, 2014 at 04:27:27PM +0200, Michael Schwendt wrote:
On Wed, 08 Oct 2014 13:46:43 +0200, Fabian Affolter wrote:
Recently I created a package python-aiohttp and this package was approved, imported, and built. But I made a mistake and took the wrong name for the package. The package runs only with Python 3. As pointed out in the review request [1] the correct name should be python3-aiohttp.
Do I need to open a rename request to fix that?
I'm not convinced it is the "wrong name". Note that you could still build a binary python3-aiohttp package from a python-aiohttp src.rpm! That's what dozens (hundreds?) of other Python Module packages do, either because they build for multiple versions of Python or because they had been added a long time before Python 3 became available.
=> I would keep it as is and not worry too much, but make sure you use the python3- prefix for the binary builds to adhere to the guidelines.
Could just using Provides: python3-aiohttp suffice?
Building two binaries for the same python stack seems a little bit of a waste of resources.
Pierre