From: Tomas Volf <~@wolfsden.cz>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: How to debug failing guix pull?
Date: Thu, 2 May 2024 16:10:52 +0200 [thread overview]
Message-ID: <ZjOe7MY5xH_1xoxx@ws> (raw)
In-Reply-To: <87jzkczvcu.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
On 2024-05-01 21:33:05 -0700, Felix Lechner via wrote:
> Hi Thomas,
>
> On Thu, May 02 2024, Tomas Volf wrote:
>
> > Updating channel 'guix' from Git repository at 'https://git.wolfsden.cz/.git/guix'...
> > guix pull: error: Git error: SSL error: 0xffff8880 - SSL - A fatal alert message was received from our peer
>
> Would you please try that again?
>
> On Thu May 2 04:22:58 AM UTC 2024, I ran this command
>
> $ openssl s_client -connect git.wolfsden.cz:443 2>/dev/null | openssl x509 -noout -dates
>
> and saw this output
>
> notBefore=May 2 03:00:16 2024 GMT
> notAfter=Jul 31 03:00:15 2024 GMT
>
> By my math, you possibly wrote your message before the certificate was
> valid, namely on or about Thu May 2 00:08:00 AM UTC 2024.
>
> Maybe Guix cared but Git didn't?
Ha, if that would be the cause it would nicely sit on the top of the pile of bad
luck I had this week. Alas, it was not the cause. I tried again and it still
fails with the same error.
What I did discover however is that the failure is specific to the debian
version of Guix. When I time-machine to 1.4.0, the pull does work. After doing
pull from the Guix upstream, the pull (from my repository) also works. Only the
debian version is affected.
Therefore I will try reporting it to debian bug tracker.
Thanks for the help :)
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-05-02 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 0:08 How to debug failing guix pull? Tomas Volf
2024-05-02 4:33 ` Felix Lechner via
2024-05-02 14:10 ` Tomas Volf [this message]
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=ZjOe7MY5xH_1xoxx@ws \
--to=~@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--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).