unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: c4droid <c4droid@foxmail.com>
To: "James R. Haigh (+ML.GNU.Guix subaddress)"
	<JRHaigh+ML.GNU.Guix@runbox.com>
Cc: help-guix@gnu.org
Subject: Re: pypi import certs issues
Date: Tue, 9 May 2023 08:55:12 +0800	[thread overview]
Message-ID: <tencent_54D2B739541685B3260C135C1320C1AC380A@qq.com> (raw)
In-Reply-To: <20230508125557.419cf21d@jrhaighs-debian-x200>

Hi, James.

On Mon, May 08, 2023 at 12:55:57PM +0100, James R. Haigh (+ML.GNU.Guix subaddress) wrote:
> Hi c4droid,
> 
> At Z+0800=2023-05-08Mon23:55:06, c4droid sent:
> > […]
> 

Thanks for the hint, I just checked my system services noticed the ntp is not install on my system,
after set it up, everything is normal.

> You appear to have sent an email from the future.  That time is currently over 4 hours into the future.  Note that certificate validation relies upon correct clock synchronisation, so without even looking into the details of what is going on with Guix, simply correcting your system clock time may in fact resolve your issue afterall.
> 
> 	Looking at the Received headers on your email, I notice that your email was in fact sent a few hours in the past:–
> 
> Mon, 08 May 2023 15:55:05 +0800
> Mon, 08 May 2023 03:55:26 -0400
> Mon, 08 May 2023 03:55:29 -0400
> Mon, 08 May 2023 03:55:31 -0400
> Mon, 08 May 2023 09:55:59 +0200
> Mon, 08 May 2023 09:56:02 +0200
> 
> These are all broadly the same time: UTC+0=07:55.  Therefore, at the time of sending, the timestamp in the Date header of your email was precisely 8 hours into the future.  Its timezone is also UTC+8, which indicates that you may have actually confused local time with system time when setting the time.  If you set your system time to UTC+8 and then on top of that your local time adds another 8 hours, at UTC+0=07:55, UTC+8+8=23:55.  That seems like a plausible explanation.
> 
> 	Furthermore, a common cause for system time being set to local time is if you dual-boot with another operating system that does not respect the system time being independent of local time.  I have heard that this is a common problem for those who dual-boot with Microsoft Windows – at least it was in the days of XP.  I don't know whether it is still a common issue in newer versions, but if you have such a dual-boot and this keeps happening, that would be a good first place to investigate to try to fix the issue.

BTW, thanks for the answer. :)

> 
> Kind regards,
> James.
> -- 
> Wealth doesn't bring happiness, but poverty brings sadness.
> Sent from Debian with Claws Mail, using email subaddressing as an alternative to error-prone heuristical spam filtering.



  reply	other threads:[~2023-05-09  1:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 17:23 pypi import certs issues c4droid
2023-05-08  1:18 ` Maxim Cournoyer
2023-05-08 15:35   ` c4droid
2023-05-08 15:55   ` c4droid
2023-05-08 11:55     ` James R. Haigh (+ML.GNU.Guix subaddress)
2023-05-09  0:55       ` c4droid [this message]
2023-05-09 13:51         ` pypi import certs issues caused by clock synchronisation issue [fixed] James R. Haigh (+ML.GNU.Guix subaddress)
2023-05-10  7:28           ` c4droid
2023-05-08 12:12     ` pypi import certs issues Maxim Cournoyer

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=tencent_54D2B739541685B3260C135C1320C1AC380A@qq.com \
    --to=c4droid@foxmail.com \
    --cc=JRHaigh+ML.GNU.Guix@runbox.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).