On 17.11.19 13:29, Simon McVittie wrote: > Package: python2 > Version: 2.7.17-1 > Severity: serious > File: /usr/bin/dh_python2 > Justification: Policy 3.5 > Control: affects -1 src:dbus-python > > As instructed by the py2removal mass-bug-filing templates, I have been > removing references to python from packages I maintain, and replacing them > with references to python2 if the Python 2 modules are still needed. > > This seems to have caused dbus-python to FTBFS when NMU'd for the python3.8 > transition: > > https://buildd.debian.org/status/fetch.php?pkg=dbus-python&arch=amd64&ver=1.2.12-1%2Bb1&stamp=1573984727&raw=0 >> Unpacking python2 (2.7.17-1) ... > ... >> Unpacking dh-python (4.20191017) ... > ... >> debian/rules override_dh_python2 >> make[1]: Entering directory '/<<PKGBUILDDIR>>' >> py3versions: no X-Python3-Version in control file, using supported versions >> dh_python2 >> make[1]: dh_python2: Command not found >> make[1]: *** [debian/rules:214: override_dh_python2] Error 127 > > /usr/bin/dh_python2 is in the python2 binary package, which is > installed, so this "command not found" shouldn't be caused by absence > of /usr/bin/dh_python2. > > As far as I can work out, it's actually caused by the absence of > the interpreter named in its first line, which is /usr/bin/python > (shells do not make it easy to distinguish between these two > failure modes). dbus-python no longer build-depends on python, so > /usr/bin/python2.7 and /usr/bin/python2 exist in the build environment, > but /usr/bin/python does not. > > I think /usr/bin/dh_python2 should now be a #!/usr/bin/python2 (or maybe > #!/usr/bin/python2.7) script, instead of a #!/usr/bin/python script.
the VCS already has the pending fix to remove dh_python2 from python2.
