On 2024-07-28 21:25, Philipp Kern wrote: > Hi, > > On 7/28/24 7:47 PM, Adrian Bunk wrote: > > when using a dw in experimental to wait for a non-buggy version of a > > package in unstable (like with libreoffice and curl due to #1077197), > > the package starts building in experimental at the right time - but > > still uses the old package. Extra-Depends works. > > > > Is there something in the priorities in experimental buildd chroots that > > results in packages in buildd-unstable being treated lower priority than > > packages in unstable? > > Looking at an experimental chroot: > > > deb https://deb.debian.org/debian unstable main contrib > > deb-src https://deb.debian.org/debian unstable main contrib non-free > > non-free-firmware > > deb https://deb.debian.org/debian experimental main contrib > > deb-src https://deb.debian.org/debian experimental main contrib non-free > > non-free-firmware > > deb https://incoming.debian.org/debian-buildd buildd-unstable main contrib > > deb-src https://incoming.debian.org/debian-buildd buildd-unstable main > > contrib non-free non-free-firmware > > deb https://incoming.debian.org/debian-buildd buildd-experimental main > > contrib > > deb-src https://incoming.debian.org/debian-buildd buildd-experimental main > > contrib non-free non-free-firmware > > So everything is pulled in and should have equal weight (there's no > preferences file) - except that it's using a different solver (aptitude?).
experimental is currently using aspcud, as aptitude fails to find a solution after a many hours on some cases (for instance kde packages). aspcud is configured the following way in sbuild.conf: | $aspcud_criteria = '-count(solution,APT-Release:=/experimental/),-removed,-changed,-new'; That said that doesn't explain the observed behaviour. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
