From: Thom R Harmon <trharmon@proton.me>
To: help-guix@gnu.org
Subject: Re: guix pull/guix upgrade often fails over VPN with TLS error message
Date: Thu, 15 Aug 2024 21:20:34 +0000 [thread overview]
Message-ID: <27114680-e10f-4029-bce9-9cbd71ec990a@proton.me> (raw)
In-Reply-To: <03c76f93-3118-4967-9baa-443e8ca0a9ab@proton.me>
Well, that was fun. Sorry, folks. I have no idea why that came through
so many times. One heck of an intro to the list though. ;)
next prev parent reply other threads:[~2024-08-15 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 13:54 guix pull/guix upgrade often fails over VPN with TLS error message Thom R Harmon
2024-08-15 21:20 ` Thom R Harmon [this message]
2024-08-17 2:01 ` Thom R Harmon
2024-08-17 2:05 ` Thom R Harmon
2024-08-17 18:14 ` Thom R Harmon via
2024-08-22 23:46 ` Thom R Harmon
2024-09-04 18:41 ` Richard Sent
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=27114680-e10f-4029-bce9-9cbd71ec990a@proton.me \
--to=trharmon@proton.me \
--cc=help-guix@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.
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).