From: "Raghav Gururajan" <rvgn@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>, iyzsong@member.fsf.org
Cc: guix-devel@gnu.org
Subject: Re: "Guix Pull" Fails
Date: Fri, 03 May 2019 16:13:04 +0000 [thread overview]
Message-ID: <7cf7b947489ff30bf1c647b05b6c6c39@disroot.org> (raw)
In-Reply-To: <2d0795aec9ae67f093c1eb6203fe80d2@disroot.org>
"Guix Pull" still fails for me. The following is the information:
address@hidden ~# guix pull
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
downloading from https://ci.guix.info/nar/gzip/1drx7dy1zakc0xs60nb0im1jbvxp11dj-isrgrootx1.pem...
isrgrootx1.pem 2KiB 486KiB/s 00:00 [##################] 100.0%
downloading from https://ci.guix.info/nar/gzip/zh3s89l1kri7r5ya0bmhil65lm0my691-module-import...
module-import 187B 62KiB/s 00:00 [##################] 100.0%
building /gnu/store/vf1ni4bdwlya3f5ii7wq6agiwdvzapmw-letsencryptauthorityx3.pem.drv...
downloading from https://letsencrypt.org/certs/letsencryptauthorityx3.pem...
/sha256 hash mismatch for /gnu/store/bcq7sqhg18b7b1q87j8z60d5hybsdafm-letsencryptauthorityx3.pem:
expected hash: 0zbamj6c7zqw1j9mbqygc8k1ykgj6xiisp9svmlif5lkbnyjhnkk
actual hash: 1kvac1dhm1d02bhrfj6l1cz1dpldz6ishb78zzvy8245zgvh7pdn
hash mismatch for store item '/gnu/store/bcq7sqhg18b7b1q87j8z60d5hybsdafm-letsencryptauthorityx3.pem'
build of /gnu/store/vf1ni4bdwlya3f5ii7wq6agiwdvzapmw-letsencryptauthorityx3.pem.drv failed
View build log at '/var/log/guix/drvs/vf/1ni4bdwlya3f5ii7wq6agiwdvzapmw-letsencryptauthorityx3.pem.drv.bz2'.
cannot build derivation `/gnu/store/paq8cw9f06lxw34aakk0vg1b9nx21cqf-le-certs-0.drv': 1 dependencies couldn't be built
guix pull: error: build of `/gnu/store/paq8cw9f06lxw34aakk0vg1b9nx21cqf-le-certs-0.drv' failed
May 3, 2019 4:27 AM, "Raghav Gururajan" <rvgn@disroot.org> wrote:
> Thank you very much Ludo.
>
> May 2, 2019 12:06 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:
>
>> Hi,
>>
>> iyzsong@member.fsf.org (宋文武) skribis:
>>
>>> Hello, thank for the report, it seems that Let's Encrypt had added the 3
>>> missing '^M' to each its pem cert file.
>>>
>>> I had pushed a fix, please try again, thank you!
>>
>> Thank you! Note that it doesn’t help much for those whose ‘guix pull’
>> refuses to run. :-)
>>
>> I’ve re-added the original .pem file on ci.guix.info (aka. berlin,
>> aka. ci.guix.gnu.org), so people should now get substitutes for it:
>>
>> https://ci.guix.gnu.org/nar/gzip/1drx7dy1zakc0xs60nb0im1jbvxp11dj-isrgrootx1.pem
>>
>> Ludo’.
next prev parent reply other threads:[~2019-05-03 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:41 "Guix Pull" Fails Raghav Gururajan
2019-05-02 13:43 ` 宋文武
2019-05-02 16:06 ` Ludovic Courtès
2019-05-03 4:27 ` Raghav Gururajan
2019-05-03 16:13 ` Raghav Gururajan [this message]
2019-05-04 8:03 ` Raghav Gururajan
2019-05-04 13:43 ` Raghav Gururajan
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=7cf7b947489ff30bf1c647b05b6c6c39@disroot.org \
--to=rvgn@disroot.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.org \
--cc=ludo@gnu.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).