Bug#901075: Please update the missing-dep-for-interpreter warning for python2
tags 901075 - moreinfo thanks Dear Axel, > Example: I changed the build-dependency in wicd from python to > python2. Now I get: > > E: wicd source: missing-build-dependency-for-dh-addon python2 => > python:any | python-all:any | python-dev:any | python-all-dev:any Ahh, getcha! Examples are great.. :) > > > >> I certainly don't want to have these warnings, at least not until > > > >> dh-python > > > >> starts generating dependencies on python2. So I assume, that I'll > > > >> leave these > > > >> new warnings for now. > > > > > > > > Sorry, can you clarify for me here — you agree that it would generate > > > > many warnings but you wish to wait for the time being...? > > > > > > I'll live with the new warnings in python-defaults. […] > Maybe it's because everyone fears that we will remove "python" > (without "2" at the end) from that list already now. That would indeed > be a bad idea (now) and I'm sure we won't do that (now). That wasn't my confusion as that seemed rather inplausible indeed. It was the apparent change from saying "please these warnings in lots of packages" to "no, don't bother with that" and then finally "I'll live with warnings in a specific package." Anyway, thanks again for clarifying. Fix incoming... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
Control: retitle -1 Please update the missing-dep-for-interpreter/missing-build-dependency-for-dh-addon/missing-python-build-dependency warnings for python2 Control: severity -1 important Hi, the change from the python package name to python2 does not only affect the missing-dep-for-interpreter warning, but also the warnings missing-build-dependency-for-dh-addon and missing-python-build-dependency. Chris Lamb wrote: > > >>> Just to be clear, won't this cause 1000s of warnings due to most >^^^ > > >>> packages depending on "python" and not "python2"? If you drop "python" in favour of "python2" in these lists, yes. What should suffice for now is to add "python2" as valid package for these kind of dependencies. Example: I changed the build-dependency in wicd from python to python2. Now I get: E: wicd source: missing-build-dependency-for-dh-addon python2 => python:any | python-all:any | python-dev:any | python-all-dev:any So there seems already a list of packages of which one of them suffices. Just add python2 to them. Same for missing-python-build-dependency: E: wicd source: missing-python-build-dependency N: N:The package appears to use Python as part of its build process in N:debian/rules but doesn't depend on Python. N: N:Normally, packages that use Python as part of the build process should N:build-depend on one of python, python-all, python-dev, or python-all-dev N:depending on whether they support multiple versions of Python and N:whether they're building modules or only using Python as part of the N:package build process. Packages that depend on a specific version of N:Python may build-depend on the appropriate pythonX.Y or pythonX.Y-dev N:package instead. Here the list is not in the tag itself but it's mentioned in the description: "should build-depend on one of python, python-all, python-dev, or python-all-dev" -- Just add python2 to the list in data/ (I assume) and the long tag description and it should be good. I assume that missing-dep-for-interpreter works the same. > > >> I certainly don't want to have these warnings, at least not until > > >> dh-python > > >> starts generating dependencies on python2. So I assume, that I'll leave > > >> these > > >> new warnings for now. > > > > > > Sorry, can you clarify for me here — you agree that it would generate > > > many warnings but you wish to wait for the time being...? > > > > I'll live with the new warnings in python-defaults. > ^^ > > I'm sorry but I'm having difficulties in understanding you. I don't understand that either. But it seems irrelevant for this bug report from my point of view. Maybe it's because everyone fears that we will remove "python" (without "2" at the end) from that list already now. That would indeed be a bad idea (now) and I'm sure we won't do that (now). :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
tags 901075 + moreinfo thanks Hi Matthias, > >>> Just to be clear, won't this cause 1000s of warnings due to most ^^^ > >>> packages depending on "python" and not "python2"? > >> > >> I certainly don't want to have these warnings, at least not until dh-python > >> starts generating dependencies on python2. So I assume, that I'll leave > >> these > >> new warnings for now. > > > > Sorry, can you clarify for me here — you agree that it would generate > > many warnings but you wish to wait for the time being...? > > I'll live with the new warnings in python-defaults. ^^ I'm sorry but I'm having difficulties in understanding you. Could you spend a few moments being a little more verbose for my benefit? Thanks in advance. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
On 08.06.2018 20:25, Chris Lamb wrote: Matthias, Just to be clear, won't this cause 1000s of warnings due to most packages depending on "python" and not "python2"? I certainly don't want to have these warnings, at least not until dh-python starts generating dependencies on python2. So I assume, that I'll leave these new warnings for now. Sorry, can you clarify for me here — you agree that it would generate many warnings but you wish to wait for the time being...? I'll live with the new warnings in python-defaults.
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
Matthias, > > Sorry, can you clarify for me here — you agree that it would generate > > many warnings but you wish to wait for the time being...? > > I'll live with the new warnings in python-defaults. I still don't 100% follow you, sorry. I asked about packages in the general archive, and you mention python-defaults..? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
Matthias, > > Just to be clear, won't this cause 1000s of warnings due to most > > packages depending on "python" and not "python2"? > > I certainly don't want to have these warnings, at least not until dh-python > starts generating dependencies on python2. So I assume, that I'll leave > these > new warnings for now. Sorry, can you clarify for me here — you agree that it would generate many warnings but you wish to wait for the time being...? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
On 08.06.2018 20:12, Chris Lamb wrote: Matthias, Please update the warning, python2 is now found in the python2/python2-minimal packages. Just to be clear, won't this cause 1000s of warnings due to most packages depending on "python" and not "python2"? I certainly don't want to have these warnings, at least not until dh-python starts generating dependencies on python2. So I assume, that I'll leave these new warnings for now.
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
Matthias, > Please update the warning, python2 is now found in the > python2/python2-minimal > packages. Just to be clear, won't this cause 1000s of warnings due to most packages depending on "python" and not "python2"? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#901075: Please update the missing-dep-for-interpreter warning for python2
Package: lintian python2-minimal 2.7.15-3 (binary) python2 => python:any | python-minimal:any (usr/bin/pyclean) #!/usr/bin/python2 python2 => python:any | python-minimal:any (usr/bin/pycompile) #!/usr/bin/python2 python2 => python:any | python-minimal:any (usr/share/python/pyversions.py) #!/usr/bin/python2 python2 => python:any | python-minimal:any (usr/bin/pyclean) #!/usr/bin/python2 python2 => python:any | python-minimal:any (usr/bin/pycompile) #!/usr/bin/python2 python2 => python:any | python-minimal:any (usr/share/python/pyversions.py) #!/usr/bin/python2 Please update the warning, python2 is now found in the python2/python2-minimal packages.
