Hi, On Thu, Mar 12, 2020 at 11:07:08AM +0100, Fabian Grünbichler wrote: > I am not sure whether we want to work around it in cargo (by defaulting > to that location, for example), but this is related to > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927889 > > libgit2 picks up an installed ca-certificates if available in the > build-env, but does not build-depend on it. if it was available, it sets > the default CA certificate location accordingly (at build time), and > cargo works. if it was not available, the certs provided by > ca-certificates need to be passed in explicitly by any user of libgit2.
As the bug is fixed in libgit2, and cargo links to the most recent version of libgit2, I think this ticket can be closed, right? (I'm hesitating to close it myself as didn't verify it really works as expected, now.) Jan
