From: Alex Kost <alezost@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Problems with downloading from https
Date: Mon, 27 Oct 2014 16:01:14 +0300 [thread overview]
Message-ID: <87d29dzmxx.fsf@gmail.com> (raw)
In-Reply-To: <87oasxj2z1.fsf@netris.org> (Mark H. Weaver's message of "Mon, 27 Oct 2014 05:06:58 -0400")
Mark H Weaver (2014-10-27 12:06 +0300) wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> Ludovic Courtès (2014-10-26 16:46 +0300) wrote:
>>>
>>>> Alex Kost <alezost@gmail.com> skribis:
>>>>
>>>>> Yes, I installed gnutls, but it didn't work because I didn't set the
>>>>> right guile paths: “guix package --search-paths” recommends
>>>>> "/usr/local/var/guix/profiles/per-user/<user>/guix-profile/share/guile/site/2.0"
>>>>> but "gnutls.scm" is actually placed in
>>>>> "/usr/local/var/guix/profiles/per-user/<user>/guix-profile/share/guile/site"
>>>>> so ‘(use-modules (gnutls))’ failed for me.
>>>>
>>>> Oh, that’s a bug of the GnuTLS package: we should pass the right
>>>> configure flag so that modules go to site/2.0. Could you do that?
>
> Alex committed this change, and it broke all https downloads in Guix,
> leading to hydra build failures. For example, see:
>
> http://hydra.gnu.org/build/132928/nixlog/1/raw
[...]
OMG! I'm sorry about that. And thanks for fixing imlib2 license issue.
I'm feeling guilty and I think I shouldn't touch anything outside
"emacs" directory. Sorry again.
--
Alex
next prev parent reply other threads:[~2014-10-27 13:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:30 Problems with downloading from https Alex Kost
2014-10-25 20:02 ` Ian Denhardt
2014-10-26 7:03 ` Alex Kost
2014-10-26 13:46 ` Ludovic Courtès
2014-10-26 19:35 ` Alex Kost
2014-10-26 21:01 ` Ludovic Courtès
2014-10-27 9:06 ` Mark H Weaver
2014-10-27 12:24 ` Ludovic Courtès
2014-10-27 12:44 ` Ludovic Courtès
2014-10-27 13:27 ` Alex Kost
2014-10-27 14:43 ` Mark H Weaver
2014-10-27 16:24 ` Ludovic Courtès
2014-10-27 16:44 ` Alex Kost
2014-10-28 8:03 ` Ludovic Courtès
2014-10-29 22:22 ` Andreas Enge
2014-10-30 7:27 ` Alex Kost
2014-10-30 7:49 ` Andreas Enge
2014-10-30 12:31 ` Alex Kost
2014-10-30 12:38 ` Andreas Enge
2014-10-30 19:30 ` Alex Kost
2014-10-30 23:07 ` Different versions of a package in the same profile? Ludovic Courtès
2014-11-01 10:46 ` Andreas Enge
2014-11-02 17:22 ` Ludovic Courtès
2014-11-02 17:39 ` Andreas Enge
2014-10-30 13:20 ` Problems with downloading from https Ludovic Courtès
2014-10-30 17:05 ` Ian Denhardt
2014-10-30 19:08 ` Alex Kost
2014-10-31 4:54 ` Ian Denhardt
2014-10-30 14:48 ` Ludovic Courtès
2014-10-27 13:01 ` Alex Kost [this message]
2014-10-27 14:32 ` Mark H Weaver
2014-10-25 21:53 ` Ludovic Courtès
2014-10-26 5:30 ` [PATCH 0/1] " Ian Denhardt
2014-10-26 5:21 ` [PATCH 1/1] README: add a note about optional GnuTLS dependency Ian Denhardt
2014-10-27 12:54 ` Ludovic Courtès
2014-10-27 10:49 ` [PATCH 0/1] Re: Problems with downloading from https Ian Denhardt
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=87d29dzmxx.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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).