From: Bone Baboon <bone.baboon@disroot.org>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: guix pull error after install i686 1.2.0
Date: Tue, 13 Apr 2021 20:26:32 -0400 [thread overview]
Message-ID: <875z0pn22v.fsf@disroot.org> (raw)
In-Reply-To: <YHNa/KbpqkPVcAUU@jasmine.lan>
Leo Famulari writes:
> On Sun, Apr 11, 2021 at 03:04:14PM -0400, Leo Famulari wrote:
>> It's expected that, before the first `guix pull`, the origin is not
>> known. The per-user view of Guix, with provenance tracking, is created
>> on the first `guix pull`.
>>
>> However, the version string should be 1.2.0. Something has gone wrong
>> on your system and caused you to "go back in time" to an earlier
>> release, the second release candidate of the 1.2.0 release.
>
> I don't think this is related to the TLS / SSL problem. That problem is
> being tracked at <https://bugs.gnu.org/46829>.
Thank you for sharing that link. It inspired several tests that I
conducted which helped me solve the problem. The issue was that the
date was significantly incorrect.
I was able to fix this with `sudo date --set='YYYY-MM-DD HH:MM:SS'`.
The changed date did not persist after a reboot and I had the same
error. To make the changed date persist after a reboot I used this
command `sudo hwclock --systohw`.
next prev parent reply other threads:[~2021-04-14 0:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 4:28 guix pull error after install i686 1.2.0 Bone Baboon
2021-04-10 9:33 ` Vincent Legoll
2021-04-10 20:12 ` Bone Baboon
2021-04-10 23:07 ` Leo Famulari
2021-04-10 23:06 ` Leo Famulari
2021-04-11 1:54 ` Bone Baboon
2021-04-11 19:04 ` Leo Famulari
2021-04-11 20:24 ` Leo Famulari
2021-04-14 0:26 ` Bone Baboon [this message]
2021-04-14 17:32 ` Leo Famulari
2021-04-14 0:14 ` Bone Baboon
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=875z0pn22v.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).