{{{> Should we run unittest when building a python package? The main drawback > is that we need to add more build-dependencies.

...


{{{> Should we run unittest when building a python package? The main drawback > is that we need to add more build-dependencies.

You could try autopkgtest.

Aside from reducing build dependencies, you can also re-test the package as the dependencies are upgraded.}}}



{{{> My package (pam-keyring) FTBFS on some buildd[1] because 'kill' is > missing. /bin/kill is part of the procps package which has a required > priority. I thought that packages with such priority should not be > added to build-deps...

It's not "Priority: required" but "Essential: yes" what allows you not to put a package in a Build-Depends.

"Essential: yes" packages are (essentially :-) a subset of required packages.}}}


{{{> * $(MAKE) install DESTDIR=pwd/debian/fspanel > > -> do *not* use pwd, but $(CURDIR).

And when using $(CURDIR), please enclose the path in double quotes (""), because $(CURDIR) may well contain spaces. There are so many packages that get this wrong...}}}