Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16792
| From | Antonio Terceiro <terceiro@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: pybuild autopkgtest |
| Date | 2025-03-14 17:00 +0100 |
| Message-ID | <KqfC1-62yv-3@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 |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Mar 14, 2025 at 07:58:38PM +0500, Andrey Rakhmatullin wrote:
>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.
Also, for most packages, the runtime dependencies should be being filled
in automatically based on the package metadata (${python3:Depends}).
Therefore, most of the time, missing runtime dependencies should be a
non-issue, except in the case of dependencies on non-Python packages.
With that said, it *would* be possible to move away from @builddeps@, or
even to filter it somehow. For Ruby packages, for example, autodep8
reads the build dependencies, and removes debhelper and gem2deb from the
list when generating the autopkgtest control file. There could be a
similar mechanism for pybuild-autopkgtest.
I was told the autodep8 maintainer accepts patches. :)
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
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