On Thu, 11 May 2017 at 15:33:41 +0200, Daniel Baumann wrote: > On 05/11/17 01:27, Aurelien Jarno wrote: > > The build daemons use aspcud as resolver for the experimental > > distribution, as aptitude is not able to handle many cases. > > why not using apt?
Because the expected behaviour for experimental and *-backports is not the same as all the other suites. In unstable, testing, stable, (old*)stable and security suites, it is sufficient to enable some apt sources, and take the newest version of each package available from any source. However, that's a bad heuristic for backports. For example, libglib2.0-0 has a jessie backport, presumably because some package that was backported needs it. However, GLib users in backports don't necessarily need that version: for example, libostree and flatpak can work with the GLib from jessie. Preferring to build against the version in jessie, and only using the version from backports if a versioned build-dep makes it strictly necessary, means that you don't need to upgrade GLib (potentially destabilizing unrelated packages) just to get the flatpak backport. Similarly, in experimental, just because a build-dependency is available in experimental at a newer version, that doesn't necessarily mean that all other experimental packages that depend on that library need the newer version. S