Bug#1010636: [Pkg-freeipa-devel] Bug#1010636: dogtag-pki: please reduce unused Build-Depends

2023-01-14 Thread Helmut Grohne
Hi Timo,

On Fri, Jan 13, 2023 at 09:39:32AM +0200, Timo Aaltonen wrote:
> Hi, the others have been dropped from the version being prepared, but
> python3-dev is needed for dh_auto_test:
> 
> dh_auto_test: warning: warning: pybuild does not support building out of
> source tree. In source building enforced.
> E: Please add appropriate interpreter package to Build-Depends, see
> pybuild(1) for details.this: $VAR1 = bless( {
>  'py3def' => '3.11',
>  'pyvers' => '',
>  'pydef' => '',
>  'builddir' => undef,
>  'py3vers' => '3.10 3.11',
>  'sourcedir' => '.',
>  'cwd' => '/<>',
>  'parallel' => '32'
>}, 'Debian::Debhelper::Buildsystem::pybuild' );
> deps: $VAR1 = [
>   'python3-cryptography',
>   'python3-distutils',
>   'python3-ldap',
>   'python3-requests',
>   'python3-setuptools',
>   'python3-sphinx',
>   'python3-urllib3'
> ];
> make: *** [debian/rules:47: build] Error 25

Thank you for reviewing my list of suggested dependencies. Would you
mind using Build-Depends: python3-dev ? Thus the dependency
would be available for tests while not encumbering cross builds.

If that still fails, consider replacing python3-dev with
"libpython3-dev, python3-dev:native" to improve cross build support.

Helmut



Bug#1010636: [Pkg-freeipa-devel] Bug#1010636: dogtag-pki: please reduce unused Build-Depends

2023-01-12 Thread Timo Aaltonen

Helmut Grohne kirjoitti 5.5.2022 klo 22.40:

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 
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  or dropped entirely.

Thanks in advance

Helmut


Hi, the others have been dropped from the version being prepared, but 
python3-dev is needed for dh_auto_test:


dh_auto_test: warning: warning: pybuild does not support building out of 
source tree. In source building enforced.
E: Please add appropriate interpreter package to Build-Depends, see 
pybuild(1) for details.this: $VAR1 = bless( {

 'py3def' => '3.11',
 'pyvers' => '',
 'pydef' => '',
 'builddir' => undef,
 'py3vers' => '3.10 3.11',
 'sourcedir' => '.',
 'cwd' => '/<>',
 'parallel' => '32'
   }, 'Debian::Debhelper::Buildsystem::pybuild' );
deps: $VAR1 = [
  'python3-cryptography',
  'python3-distutils',
  'python3-ldap',
  'python3-requests',
  'python3-setuptools',
  'python3-sphinx',
  'python3-urllib3'
];
make: *** [debian/rules:47: build] Error 25


--
t