Hi Stephen,
I looked into why it runs mkkey and couldn't figure out much. Let me
write down what I know:
* It generates an RSA public/private key pair.
* The public key is installed to /usr/share/doc.
* The private key is used in some other way during the build (the
comments talk about obfuscation).
Thus I think that removing the public key should be possible, but it
doesn't help, because the private key gets embedded elsewhere and I
don't understand what it is being used for.
On Wed, Apr 10, 2019 at 04:03:14PM +0200, Stephen Kitt wrote:
> I have a patch which builds mkkey using the build CC, which makes the build
> fail earlier because we don't have libgmp, so that would fix the endless
> build ;-). Helmut, do we have any way of specifying native build-deps? IIRC
> we don't yet, is that still the case?
Thank you for working on this. Indeed making it fail earlier would help
a lot. This is the only package that breaks the crossqa.d.n
infrastructure.
The annotation you are looking for is :native. It can only be used in
Build-* relations and never in binary package relations. In this case,
you likely want to depend on libgmp-dev twice, because other parts need
it for the host architecture:
Build-Depends: libgmp-dev, libgmp-dev:native
This might look odd, but it actually works (as libgmp-dev is Multi-Arch:
same) and for native builds these dependencies are identical.
I'd appreciate if you could go ahead with your changes (with or without
libgmp-dev:native, just make it fail reliably rather than loop).
Helmut
