On Thu, 10 Oct 2024 Paul Gevers <elb...@debian.org> wrote:> I'm filing this bug for transparency, I'm not actually expecting us to > fix it considering the upcoming new solver in apt. > > In the gnome-shell transition, we were debugging failures in the > autopkgtest of gnome-shell-pomodoro which shows that during the build > (due to the needs-build restriction) autopkgtest doesn't apply the > fallback of using everything from the source suite that it does while > running the test. This is inconsistent. > > Paul > > https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnome-shell-pomodoro/52897268/log.gz
Hi, pinning is also inconsistent when doing the initial dist-upgrade of the testbed, as can be seen in this case (after all the noise due to an openstack failure and retry): https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-plucky/plucky/amd64/liba/libalgorithm-merge-perl/20241022_010901_b3072@/log.gz I agree the way forward is using the new solver and --no-string-pinning, but details are to be worked out. Also, the fallback logic (should we end up keeping any) should be moved in some common function, like _run_apt_command(). Paride
