Control: tags -1 moreinfo Carsten,
On Friday, October 4, 2024 11:18:04 AM MST Carsten Schoenert wrote: > the Python policy hasn't got updates and adjustments since years, a lot > of things are a bit outdated e.g. how to handle Python2 based packages. > > The part Sandro was referring to is §4.3 > https://www.debian.org/doc/packaging-manuals/python-policy/#module-package-nam > es > > This isn't a rule of MUST, it's SHOULD and this is good. I think this > package is a good example why. > User will not search for python3-trezorlib because the upstream name is > trezor. The module name is basically important for programmers because > they need to know which module they need to use and therefore include. Thank you for the detailed explanation. I am inclined to follow your advice and leave the package names as is. Sandro, As you were the original filer of the bug, I want to give you a chance to respond if you still feel that renaming the binary package is appropriate. If I don’t hear from you in a reasonable amount of time I will close the bug report. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
