Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: pybuild autopkgtest

From Carsten Schoenert <c.schoenert@t-online.de>
Newsgroups linux.debian.maint.python
Subject Re: pybuild autopkgtest
Date 2025-03-14 15:10 +0100
Message-ID <KqdTA-61Ex-13@gated-at.bofh.it> (permalink)
References (2 earlier) <KqboJ-6010-7@gated-at.bofh.it> <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>
Organization linux.* mail to news gateway

Show all headers | View raw


Hello Frederic,

Am 14.03.25 um 14:17 schrieb PICCA Frederic-Emmanuel:
> I want to run the same test suite (which is most often provided by 
> the upstream in order to test the package), during the build and as
> installed.
> 
> but @builddep@ are not the dependency in order to run the test as
> installed but during the build.
> 
> I need to check that my python-<package> dependencies and the
> specific tests dependencies is a working subset of @builddep@ for
> these tests.
then drop this variable and list all the packages that are needed to get 
the upstream tests running.

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.

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

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

-- 
Regards
Carsten

Back to linux.debian.maint.python | Previous | NextPrevious 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