Groups > linux.debian.maint.python > #16785

Re: pybuild autopkgtest

From	PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>
Newsgroups	linux.debian.maint.python
Subject	Re: pybuild autopkgtest
Date	2025-03-14 15:50 +0100
Message-ID	<Kqewh-61Tu-5@gated-at.bofh.it> (permalink)
References	(3 earlier) <Kqbyp-604r-11@gated-at.bofh.it> <KqbRL-60bi-5@gated-at.bofh.it> <KqbRL-60bi-3@gated-at.bofh.it> <Kqcut-60E4-5@gated-at.bofh.it> <KqdTA-61Ex-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> I've dropped using @builddep@ in general within the packages I'm
> involved to achieve exactly what Andrey has written, I want to detect
> broken or missing dependencies, broken tests by changed dependencies in
> other depending packages. And don't want to get this hidden by packages
> that are within @builddep@ that potential pull in the other then needed
> packages.

exactly

> Using @builddep@ is mostly not useful for testing Python packages.

does the python tools provide a way to get the runtime dependencies or the test dependencies of a package ?

This would allow to automatize a lot'of our packaging job, upgrade etc..

> So yes, need to figure out which packages then you want to have listed
> in d/t/control to make the tests pass.

yes.

I will use the doc snipset and customize it to have the right dependencies.

But I am wondering if the best would not be to have something more declarative like the extra_dependencies in order to supersede the full dependencies instead of just adding more dependencies.

Fred

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

pybuild autopkgtest picca <picca@debian.org> - 2025-03-14 12:00 +0100
  Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 12:00 +0100
    Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 12:30 +0100
      Re: pybuild autopkgtest Jeroen Ploemen <jcfp@debian.org> - 2025-03-14 12:40 +0100
      Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 12:40 +0100
        Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 13:00 +0100
          Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 13:40 +0100
            Re: pybuild autopkgtest Carsten Schoenert <c.schoenert@t-online.de> - 2025-03-14 15:10 +0100
              Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 15:50 +0100
                Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:20 +0100
                Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:50 +0100
                Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 17:20 +0100
            Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:00 +0100
              Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:30 +0100
                Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:50 +0100
              Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:40 +0100
              Re: pybuild autopkgtest Antonio Terceiro <terceiro@debian.org> - 2025-03-14 17:00 +0100
        Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 13:10 +0100

csiph-web