unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 39615@debbugs.gnu.org
Subject: bug#39615: LetsEncrypt root certificate hash changed
Date: Sun, 16 Feb 2020 10:52:00 +0100	[thread overview]
Message-ID: <87h7zq97wf.fsf@nckx> (raw)
In-Reply-To: <87zhdjym2z.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Chris,

Christopher Baines 写道:
> However, while this change might avoid the problem with guix 
> pull in the
> future, I still a bit stuck. I got this from a fresh install of 
> Guix on
> the Overdrive machine I have (aarch64-linux).

I guess I've found my purpose this week and it's ‘mirroring old 
shit’.

This is not at all a solution, but you can ‘guix download’ the old 
.pem files here[0] and hopefully be on your merry way.

> I'm hoping that I'll be able to install git and the Guix 
> dependencies,
> download the repository, and then get a newer version of Guix 
> that way,
> but I'm guessing this will still be a problem for other 
> aarch64-linux
> machines unless there's a substitute out there somewhere.

Indeed, and not just aarch64…

Kind regards,

T G-R

[0]: https://www.tobias.gr/guix

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-02-16  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 15:33 bug#39615: LetsEncrypt root certificate hash changed Christopher Baines
2020-02-15 16:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-16  8:26   ` Christopher Baines
2020-02-16  9:52     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-02-16 10:11       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-16 10:46       ` Christopher Baines

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=87h7zq97wf.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=39615@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=me@tobias.gr \
    /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).