From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:49060) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ir8ep-0005uU-Mg for guix-patches@gnu.org; Mon, 13 Jan 2020 17:58:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ir8eo-0005p1-Nh for guix-patches@gnu.org; Mon, 13 Jan 2020 17:58:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54393) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ir8en-0005oU-JB for guix-patches@gnu.org; Mon, 13 Jan 2020 17:58:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ir8en-0004oD-JD for guix-patches@gnu.org; Mon, 13 Jan 2020 17:58:01 -0500 Subject: [bug#38873] [PATCH] gnu: curl: Make libcurl respect SSL_CERT_{DIR, FILE} Resent-Message-ID: From: Marius Bakke In-Reply-To: <20200102171826.v4j3d35ocx7tvp2j@zdrowyportier.kadziolka.net> References: <20200102171826.v4j3d35ocx7tvp2j@zdrowyportier.kadziolka.net> Date: Mon, 13 Jan 2020 23:57:28 +0100 Message-ID: <871rs3vuav.fsf@devup.no> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Jakub =?UTF-8?Q?K=C4=85dzio=C5=82ka?= , 38873@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Jakub K=C4=85dzio=C5=82ka writes: > * gnu/packages/curl.scm (curl-7.66.0): Use patch. > * gnu/packages/patches/libcurl-use-ssl-cert-env.patch: New file. > > This fixes the SSL errors occuring when trying to use rust:cargo's > download functionality. > > As an additional advantage, this will probably allow removing some > package-specific work-arounds that have already been made. I have > found such work-arounds in cmake and kodi, but am not familiar enough > with either to confidently remove them. Thanks! We should probably adjust the (native-search-paths ...) field of cURL to account for these new variables too. Can you also rebase it on 'core-updates'? From=20reading the upstream discussion, there does not seem to be any inherent problems with the patch. So, LGTM. Are you willing to maintain it when it inevitably requires porting to newer versions? :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl4c9dgACgkQoqBt8qM6 VPoYIQgAzZvo3VWMAcId3YFlqfyG6XbYz0jsue7a/25aImQ/UU2lJ3nGs6tpCL7x wulW/Cd7CRa/Pnbn4IqAv3hZqt4DrDsA/d4qVFAUNbBrtm5NzgIJc53UqavzxVpj g2AVrgex4QjQONnOatwdXtPUF/dJ9steAodmstVlrFE8xZMM09x+S62ng6S18g0L GewVkzbk/jAO6hytItwq6TsXFXiY4uH5B9naVRiRoSB7pDIKPm4623jAIPiNgzrs 0toARGrTxQ4HeXDAYuLPk957Be533z1VtHteo2kN+JgdYZTq4W/8dI59Pf+65SjB fBgt2dk/NsdYQPJUbXthCjJfh1I3qQ== =lDnc -----END PGP SIGNATURE----- --=-=-=--