Thanks for the rapid followup, Felix! I really appreciate your ongoing attention to detail with lintian. It's a very useful tool. On Fri 2021-02-12 19:21:39 +0000, Felix Lechner wrote: > Based on the information we have, the unversioned /usr/bin/python is > going away in the upcoming 'bullseye' release. The corresponding > changes were made in response to this merge request > > https://salsa.debian.org/lintian/lintian/-/merge_requests/334 > > in this and surrounding commits: > > https://salsa.debian.org/lintian/lintian/-/commit/69d52d7b4c9dbf391b23dced6e6de920905f54ac > > Please file a bug for the unversioned Python interpreter to be > recognized as valid, if the information we have about the 'bullseye' > release is incorrect. I don't have any more information than you do about the specific plan for python in bullseye -- but what you're suggesting seems both plausible and reasonable to me. I was worried about the intended semantics for what "python" means, but https://www.python.org/dev/peps/pep-0394/#recommendation has this recommendation for distributors: >>> When packaging third party Python scripts, distributors are >>> encouraged to change less specific shebangs to more specific >>> ones. This ensures software is used with the latest version of >>> Python available, and it can remove a dependency on Python 2. The >>> details on what specifics to set are left to the distributors; >>> though. Example specifics could include: >>> >>> - Changing python shebangs to python3 when Python 3.x is supported. So this is probably something I should be fixing when packaging gpgme itself. Perhaps lintian could include a pointer to this reference in the description text for example-unusual-interpreter. Regards, --dkg
Attachment:
signature.asc
Description: PGP signature