Félix Sipma <felix+deb...@gueux.org> writes: > They just run "python3 setup.py install" > (https://github.com/scheibler/khard/issues/231): > [...] > > For my part, I "just" build the debian package with "gbp buildpackage", > and with "dh $@ --with python3 --buildsystem=pybuild" in debian/rules. > > The solutions I say are: I can keep the patch in the package (without > really understanding the need for it) or try to convince upstream to > merge it (but they can't reproduce the problem, so why would they do > that?). In both cases, probably others will encounter the same problem > in other packages... It would be nice to fix the problem once for all > (if possible :)).
Just FYI, https://bugs.debian.org/940728 describes a similar problem, although there the unhandled files are Python source files. pybuild seems to handle things different from plain setup.py. Cheers Ole
