On Sat, Jun 09, 2018 at 10:26:05AM +1000, Ben Finney wrote: > The package currently has (discovered when investigating this > behaviour, so thank you) a bug in its definition of the ‘debian/rules’ > target ‘override_dh_auto_build’. > > I'm unsure about Debhelper failing to find the sequence for ‘python2’. > That should already be pulled in when you install the build > dependencies. Maybe this is complicated by the > ‘override_dh_auto_build’ bug. > > I am adding this change, please let me know whether it corrects the > package behaviour for you:
Sorry, I can't test external packages easily in my setup. Instead, I'll be more precise so that you can reproduce this too: I'm using "sbuild --arch-all --no-arch-any" on a clean chroot, which is what an official autobuilder would do to build the arch-indep packages. By looking at the debian/control file, this seems to be a bad interaction between Build-Depends / Build-Depends-Indep / Build-Depends-Arch. My feeling is that you are assuming some packages to be present when in fact they do not necessarily have to be present according to debian/control when building only the arch-independent packages. (And this would be why debhelper does not "find" the python2 thing). Hope this helps.
