On 17.11.19 20:53, Simon McVittie wrote: > Control: tags 944949 + moreinfo > > On Sun, 17 Nov 2019 at 19:07:39 +0000, Matthias Klose wrote: >> Please add an explicit build dependency on dh-python. > > As far as I can see it's been explicit since 2015. Is anything more > needed here? > > Note that the FTBFS with > > dh_python2 > make[1]: dh_python2: Command not found > > seems to be because /usr/bin/dh_python2 is a #!/usr/bin/python script in > a package that doesn't depend on python (#944894). The misleading > "Command not found" is similar to this: > > $ cat > Makefile > all: > ./script > $ cat > script > #!/usr/bin/does-not-exist > $ chmod +x script > $ make > ./script > make: ./script: Command not found > make: *** [Makefile:2: all] Error 127 > > I have a workaround which I believe should still be harmless after > dh_python2 moves out of python2 (presumably into dh-python?), which I'll > upload soon. > > If that doesn't work, I'll temporarily re-add the python B-D so the > python3.8 transition can go through, and remove it after #944894 is > resolved. > > It's unfortunate that the python3.8 transition, the effort to replace > references to python2 with python, and the migration of dh_python2 from > python2 to dh-python (?) are happening at the same time and affect > overlapping sets of packages. Perhaps one (or more) of these could be > deferred until one of the others has been done?
this specific issue is unrelated. dh_python2.py was calling python, not python2. now fixed in an interim upload. Still waiting for feedback from my co-maintainer how to proceed with the dropped dh-python dependency in python3-defaults.
