Sven Hartge wrote:
> Sven Hartge wrote:
>> 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.
> Hmm, I
On Thu, Jan 17, 2019 at 09:29:58PM +0100, Thomas Koch wrote:
Remarks: -
https://www.debian.org/doc/debian-policy/ch-binary.html#virtual-packages
links to virtual-package-names-list.yaml instead of .txt.
That's not the bug, the bug is the yaml file not being present at the
destination of the
Sven Hartge wrote:
> 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.
Hmm, I may see the reason for your
Thomas Koch wrote:
> We're trying to package nix. Its d/control[1] 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
>
On Thu, 17 Jan 2019 at 21:29:58 +0100, Thomas Koch wrote:
> We're trying to package nix. Its d/control[1] 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
>
We're trying to package nix. Its d/control[1] 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
6 matches
Mail list logo
