On Mon, 5 Aug 2024 21:12:36 +0200 Paul Gevers <elb...@debian.org> wrote: > Hi, > > On 05-08-2024 15:46, Simon McVittie wrote: >> To avoid this, I think it would have to grow a new command-line >> option to tell it something like: "pin all binary packages from >> src:rust-async-executor to source version 1.12.0-3, at a high >> priority". > > I thought we were doing that *until* the fallback lifts all pinning. > Rest assured that in the past I worked [1, 2] to prevent the > fallback, because I consider it wrong, but it helped in quite some > cases where the outcome is acceptable in the end. The price was that > if it still fails, it more confusing to figure out. > > I have good hopes that the version 3 solver of apt is going to > improve things, I'm not sure if it would have helped in this case. > But maybe it will enable us to disable the fallback again.
I think solver3 could allow us to stop using the fallback, at least when the apt version on the testbed is new enough. When testing on stable releases the fallback is likely not that useful, as the packages to test are likely to be minor updates not requiring to relax pinning in most cases, so my hope is that we'll be able to drop it. This said, I think we should still make autopkgtest do some stricter pinning on the package under test, as Simon mentioned, but I hope that is doable without growing a new command line option. -- Paride
