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

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:50 +0100
Message-ID	<Kqfsl-62v1-31@gated-at.bofh.it> (permalink)
References	(3 earlier) <KqbRL-60bi-3@gated-at.bofh.it> <Kqcut-60E4-5@gated-at.bofh.it> <KqdTA-61Ex-13@gated-at.bofh.it> <Kqewh-61Tu-5@gated-at.bofh.it> <KqeZj-62kp-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> Runtime sure, and we already use that.


Do you have a pointer to this logic, It would be great to be able to update the B-D via this mecanisme like we do with cabal-debian.
We should have a pip-debian which could take care of upgrading the B-D in the control file each time we integrate a new upstream version.

> Test no, they aren't even specified
> in an uniform way in the upstream code (it could be e.g. a
> tests/requirements.txt, one or several lists of deps in tox.ini or a
> custom pip install line in the CI job definition, or nothing at all if
> they run tests only locally and manually).

This is a pity..., it will defeat automatic packaging...

> That makes sense. Or maybe it should get only the B-D annotated with
> !nocheck if those exist.

this is something I was wondering also.

but usualy we do not tag with <!nocheck> the runtime dependecies in the B-D field.

Do we need to have the run-time in the B-D in order to build the package (without running the test ?)

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