Source: dogtag-pki Version: 11.0.3-4 User: debian-cr...@lists.debian.org Usertags: cross-satisfiability
dogtag-pki cannot be cross built from source, because its Build-Depends are not satisfiable. The problems are numerous, so instead of looking into them in detail, I looked for low hanging fruit: unused Build-Depends. Since dogtag-pki is mostly reproducible (except for the build path), there is a relatively easy technique for identifying unused Build-Depends: * Build dogtag-pki * Build dogtag-pki with as many Build-Depends moved to Build-Conflicts as possible while also passing DEB_BUILD_OPTIONS=nocheck. Use the same build path. * Verify that both builds produce bit-identical results. So that's what I did and the following dependencies could be moved to Build-Conflicts: * libjaxp1.3-java * libxalan2-java * policycoreutils * python3-dev * python3-nss Of course, Build-Conflicts is not the aim, but it ensures that the packages are really gone and not pulled by some other dependency for the purpose of testing. Then, disabling tests via DEB_BUILD_OPTIONS=nocheck of course may have found test dependencies. And finally, packages may contain pre-build artifacts that are only rebuilt when the relevant build tools are available, so we cannot just delete these packages from Build-Depends. Some will have to stay. Some may be annotated <!nocheck> and some can be dropped. Can I ask you to review each of the mentioned 5 dependencies? I'd hope that all of them can be annotated <!nocheck> or dropped entirely. Thanks in advance Helmut
