On Thu, 19 Sep 2024 at 23:40:55 +0800, trim21 wrote: > I recently found that you are packaging this pypi package in debian > testing and unstable repo as `python3-transmissionrpc`, and it's > originally pypi package transmissionrpc. > > This package is forked from the original pypi transmissionrpc package > and renamed as transmission-rpc on pypi. > > I don't want it to cause confusion between these two package names, > can we rename it to `python3-transmision-rpc` instead?
Debian's policy is to name Python packages according to the name that you can `import`, not the PyPI name: https://www.debian.org/doc/packaging-manuals/python-policy/index.html#module-package-names What name do you `import` to use this package? If you would use `from transmissionrpc import ...` then python3-transmissionrpc is considered correct for Debian, regardless of whether that module name is provided by a fork or by the original. But if you would use `from transmission_rpc import ...` then yes, it should ideally be renamed to python3-transmission-rpc (underscores are not allowed in Debian package names, so the convention is to replace them with dashes) because it no longer has an API that is compatible with the transmissionrpc module. Renaming a package is not something that the package's maintainer can do immediately - it requires approval from the archive administrators, who are very busy and have a long queue of packages needing review in https://ftp-master.debian.org/new.html - so if a rename is required, please be patient. smcv
