Re: confused about virtual build-depends libcurl-dev
- Date: Fri, 18 Jan 2019 08:13:24 +0100
- From: Sven Hartge <sven@xxxxxxxxxxxxx>
- Subject: Re: confused about virtual build-depends libcurl-dev
Thomas Koch <thomas@xxxxxxx> wrote:
> We're trying to package nix. Its d/control currently says:
> build-depends: libcurl4-gnutls-dev | libcurl4-openssl-dev | libcurl-ssl-dev
> When I build it on my own machines with sbuild, then it gets built
> with libcurl4-gnutls-dev. On salsa it gets built with
> libcurl4-nss-dev. How can there be a difference in selection?
I am the one responsible for a change in the build-depdendency resolver
used by the Salsa-CI pipelines.
Before the change, they used "apt-get build-dep ." to gather the
build-deps, but this didn't work for *-backports or experimental or
Jessie. Also it would pull in recommended packages, which could make the
build unreproducible and is agains Policy 4.2.
I changed the resolver to use a combination of mk-build-deps and
aptitude, the same as sbuild and pbuilder use to resolve build-deps, to
better handle alternatives.
You may have hid an edge case I didn't encounter during my testing.
>  https://salsa.debian.org/debian/nix/blob/kaiha/wip/debian/control
Do you have a pipeline log on Salsa showing the mis-selection of
build-deps? During a cursory glance I could only find logs showing the
use of libcurl4-gnutls-dev.
Sigmentation fault. Core dumped.