all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Van Ymeren <adam@vany.ca>
To: ng0+guixpatches@n0.is
Cc: guix-devel@gnu.org
Subject: Re: [bug#30165] [PATCH] gnu: gnurl: Add '--with-ca-bundle' path to	configure-flags.
Date: Tue, 23 Jan 2018 20:55:35 -0500	[thread overview]
Message-ID: <87h8rchvfs.fsf@vany.ca> (raw)
In-Reply-To: 20180118230727.16742-1-ng0+guixpatches@n0.is


Regarding https://debbugs.gnu.org/30165

gnurl is failing to build on my system and I think this patch is to
blame.  Why is gnurl referencing something under the root filesystem
rather something provided by an input?  Shouldn't we provided
ca-certificates.crt from an input and reference that?

I guess we want to be able to to change what certificates that gnurl
accepts without rebulding the package, but I think we need something to
provide that file when building the package in the first place, or
disable the relelvant tests.

For reference the build error I'm seeing is
==========================
test 0324...[TLS-SRP with server cert checking]

curl returned 77, when expecting 51
 exit FAILED

 - abort tests

=========================

From the curl man page, exit code 77 means "Problem with reading the SSL
CA cert (path? access rights?)."

             reply	other threads:[~2018-01-24  1:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  1:55 Adam Van Ymeren [this message]
2018-01-24 11:52 ` [bug#30165] [PATCH] gnu: gnurl: Add '--with-ca-bundle' path to configure-flags ng0+guixpatches
2018-01-24 13:23   ` ng0
2018-01-24 14:40     ` Ricardo Wurmus
2018-01-24 17:00     ` Adam Van Ymeren
2018-01-24 17:00     ` Adam Van Ymeren
2018-01-24 17:56       ` ng0
2018-01-24 18:15         ` Adam Van Ymeren
  -- strict thread matches above, loose matches on Subject: below --
2018-01-18 23:07 ng0+guixpatches

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8rchvfs.fsf@vany.ca \
    --to=adam@vany.ca \
    --cc=guix-devel@gnu.org \
    --cc=ng0+guixpatches@n0.is \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.