Hello, here are my comments about this bug.
The first question is: Does the name of the package libsane1 match the rules? This has to be answered clearly. In the Debian Policy it says in section 8.1 paragraph 2 " Normally, the run-time shared library and its SONAME symlink should be placed in a package named librarynamesoversion, [...]". Thus, the packet name libsane1 does not contradict the rules of the policy and is therefore not objectionable. The next question is to decide when to change the name. The run-time shared library must be placed in a package whose name changes whenever the SONAME of the shared library changes. [...]". The "must" implies IMHO's obligation to change the package name accordingly. But this was not done a long time ago for reasons unknown to me. The fix of this bug "must" therefore be allowed by the maintainer. So I take the liberty of closing this bug. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key : 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home.
signature.asc
Description: This is a digitally signed message part
