Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1269617
| From | Paul Gevers <elbrus@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1105203: Sets widely matching apt pin priority, causing ansible autopkgtest to fail |
| Date | 2025-11-09 10:20 +0100 |
| Message-ID | <LP9Kx-bCz3-1@gated-at.bofh.it> (permalink) |
| References | <KLUKe-2NTz-5@gated-at.bofh.it> <KLUKe-2NTz-5@gated-at.bofh.it> <KLUKe-2NTz-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Control: block -1 by 1052119 Hi Lee, On Tue, 13 May 2025 12:07:32 +0200 Lee Garrett <debian@rocketjump.eu> wrote: > While I believe it's a bug in python3-apt or ansible-core, I think we should be > more cautious about setting the pin priority, as this might also affect other > software doing similar tests. AFAICS this pinning shouldn't be needed, as the > package being tested should always have a higher version number than the one in > the apt archive. > > So my questions are: Is this really needed? And if yes, could we instead do a > narrower apt pinning at runtime to the specific packages in question? Over the years, we've tried multiple things to improve how we're ensuring that the right packages are tested. We have ideas how to further improve things, but it's extremely hard to do, because there are so many things to consider. See e.g. bug #1052119 as an example where we had to revert an improvement related to pinning, because it didn't play nicely (yet). Paul
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1105203: Sets widely matching apt pin priority, causing ansible autopkgtest to fail Paul Gevers <elbrus@debian.org> - 2025-11-09 10:20 +0100 Bug#1105203: Sets widely matching apt pin priority, causing ansible autopkgtest to fail Paride Legovini <paride@debian.org> - 2025-11-11 18:40 +0100
csiph-web