On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote: > You should rather work towards defining a common build environment > standard in Debian [...]
You must be joking. There is already a "common build environment standard", and it's called the set of build essential packages, of which gnupg is not (not the old gnupg, not the new gnupg, not the old gnupg2, and not the new gnupg1). Everything which is required to build and it's not in build essential must go in build-depends. What part of this standard (the build essential set of packages, the one that really counts, not the list of packages in the package builder of the day) is the one that you don't understand? It's in Policy 4.2, here is a quote: If build-time dependencies are specified, it *must* be possible to build the package and produce working binaries on a system with *only* essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships). This is what you are still not doing with your pbuilder example. You say "unreproducible", I say unwillingess to reproduce. This is a must directive in policy, and everybody agrees that missing build-depends are RC. Do you still disagree that this is severity serious? __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.