Bug#909510: please add a lintian note to inform/warn about python in the shebang (instead of python2/python2.7)
On 15.01.19 00:48, Chris Lamb wrote:
> Adrian Bunk wrote:
>
>>> There is discussion upstream about updating PEP 394 to recommend soft-linking
>>> python to python3 on newer distributions. Not a good idea from my point of
>>> view, but it would be better if we remove the usage of python as a shebang in
>>> our packages. Replacing that with python2 or python2.7 should be easy and safe.
>>> It would be nice if lintian could help with this task. Maybe first as a note so
>>> we can get an overview.
>>
>> Isn't it too late for such a lintian warning to make sense?
>>
>> We are only 5.5 months away from the buster freeze, and there
>> is no realistic chance of fixing this archive-wide until then.
>>
>> Unless plans have changed python2 will not be part of bullseye,
>> and for that to happen removal of any python2 usage has to start
>> aggressively directly after the release of buster.
>> The lintian warning would be moot then.
>>
>> If such an upstream change will be in bullseye or later,
>> the realistic solution would be to add a
>> Breaks: python-minimal
>> Replaces: python-minimal
>> to python3-minimal.
>
> Any followup to this, Matthias?
I don't agree with Adrian's view. If there is need to keep 2.7, then we should
keep it to keep things running like mercurial, and afaik samba isn't yet ready
for 3.x. So yes, such a warning makes sense for bullseye.
It's ok to stop building unused python 2.x nodules once buster released, but
that doesn't mean that we already are at the point to "aggressively to remove
any python2 usage".
Reply to: