From: Marius Bakke <mbakke@fastmail.com>
To: "Jakub Kądziołka" <kuba@kadziolka.net>, 38873-done@debbugs.gnu.org
Subject: bug#38873: [PATCH v2 core-updates] curl: Make libcurl respect SSL_CERT_DIR, SSL_CERT_FILE
Date: Wed, 15 Jan 2020 00:37:20 +0100 [thread overview]
Message-ID: <87r201vccv.fsf@devup.no> (raw)
In-Reply-To: <20200114165921.epqysoaydxxqm5ye@zdrowyportier.kadziolka.net>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Jakub Kądziołka <kuba@kadziolka.net> writes:
> * gnu/packages/patches/libcurl-use-ssl-cert-env.patch: New file.
> * gnu/packages/curl.scm (curl)[source]: Use the patch.
> [native-search-paths]: Add the new variables.
> ---
> gnu/packages/curl.scm | 20 ++++--
> .../patches/cmake-curl-certificates.patch | 2 +
> .../kodi-set-libcurl-ssl-parameters.patch | 2 +
> .../patches/libcurl-use-ssl-cert-env.patch | 64 +++++++++++++++++++
> 4 files changed, 84 insertions(+), 4 deletions(-)
> create mode 100644 gnu/packages/patches/libcurl-use-ssl-cert-env.patch
The commit message forgot to mention the changed patches. However I
opted to remove them, as the Kodi and CMake patches are harmless even
with your patch, but will encourage you to fix them regardless. ;-)
Also added the new patch to gnu/local.mk and adjusted indentation of the
cURL comments.
Pushed as a76a343082d61d5303b61a9e4cbde4ab8515a1e7, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-01-14 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 17:18 [bug#38873] [PATCH] gnu: curl: Make libcurl respect SSL_CERT_{DIR, FILE} Jakub Kądziołka
2020-01-12 16:32 ` [bug#38873] Patch submitted upstream Jakub Kądziołka
2020-01-13 22:57 ` [bug#38873] [PATCH] gnu: curl: Make libcurl respect SSL_CERT_{DIR, FILE} Marius Bakke
2020-01-14 16:59 ` [bug#38873] [PATCH v2 core-updates] curl: Make libcurl respect SSL_CERT_DIR, SSL_CERT_FILE Jakub Kądziołka
2020-01-14 23:37 ` Marius Bakke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r201vccv.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38873-done@debbugs.gnu.org \
--cc=kuba@kadziolka.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).