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

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 16:40 +0100
Message-ID	<Kqf8Z-62nD-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> <KqeFY-61Xq-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> You said "I want to check during the autopkgtest that the runtime
> dependencies are well defines in the package" and for that you shouldn't
> have any additional packages installed, but to run tests you normally need
> additional packages, usually quite a lot of them.

I was spoken about the test specific dependencies.

not the dependencies of the packages (dependencies which are imported in the upstream module code).

> Most of them are, considering that the build process of a pure-Python
> package is moving files around, building docs and running tests.
> Which ones aren't? sphinx and friends?

So how do we guaranty that the listed dependencies (from the  upstream, supposing there are right ;) are well define in the binary package dependencies ?

I just tell this because entry_point checking for the module dependencies.
So sometimes I get <something> is missing when running entry points.

> Yes, I just don't think the difference between @builddep@ and actual test
> deps is big enough to matter for this task and, as I wrote above, this
> won't help for your originally stated task so I'll assume you didn't
> actually want that.

thanks for your time

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