all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: julien lepiller <roptat@lepiller.eu>
Cc: 36363@debbugs.gnu.org
Subject: bug#36363: let's encrypt hash mismatch
Date: Mon, 24 Jun 2019 20:44:07 +0200	[thread overview]
Message-ID: <87pnn2su14.fsf@nckx> (raw)
In-Reply-To: <20190624192302.0eccdd72@tachikoma.lepiller.eu>

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

Julien,

Julien Lepiller wrote:
> trying to run guix pull on the overdrive at my place to try and 
> fix a
> bug in openssh which doesn't start at boot, I get this error 
> message:

[…]

>  letsencryptauthorityx3.pem  2KiB     385KiB/s 00:00
>  [##################] 100.0% sha256 hash mismatch
>  for /gnu/store/1drx7dy1zakc0xs60nb0im1jbvxp11dj-isrgrootx1.pem:
>  expected hash: 
>  0zhd1ps7sz4w1x52xk3v7ng6d0rcyi7y7rcrplwkmilnq5hzjv1y
>  actual hash: 
>  0zycy85ff9ga53z1q03df89ka9iihb9p8bjhw056rq2y4rn3b6ac

This will keep happening until we find(/create) a versioned URL 
for these files.  Let's Encrypt like to change them in place.

The last time this happened they'd added CR/LF line endings for no 
reason at all, but this time I don't have the old version around 
anymore…

Kind regards,

T G-R

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

  reply	other threads:[~2019-06-24 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 17:23 bug#36363: let's encrypt hash mismatch Julien Lepiller
2019-06-24 18:44 ` Tobias Geerinckx-Rice [this message]
2019-06-24 20:09 ` Ludovic Courtès
2019-07-21 23:12   ` Chris Marusich
2019-07-22 10:34     ` Ludovic Courtès
2020-10-09 12:04 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=87pnn2su14.fsf@nckx \
    --to=me@tobias.gr \
    --cc=36363@debbugs.gnu.org \
    --cc=roptat@lepiller.eu \
    /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.