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:14:52 -0400 [thread overview]
Message-ID: <877dl5n2mb.fsf@disroot.org> (raw)
In-Reply-To: <YHNILpuS7TAmzjtN@jasmine.lan>
Leo Famulari writes:
>> The output of `guix describe`:
>> ```
>> guix describe: error: failed to determine origin
>> hint: Perhaps this `guix' command was not obtained with `guix pull'? Its version string is 1.2.0rc2-1.0d4b1af.
>> ```
>
> This isn't quite right.
>
> 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.
The steps I did after the install:
1) ping a website
2) guix pull (fails)
3) reconfigure system
4) guix describe
I think it is step 3 which caused the rollback to the release
candidate. I even received a warning that running a reconfigure before
running `guix pull` could downgrade the system.
prev parent reply other threads:[~2021-04-14 0:16 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
2021-04-14 17:32 ` Leo Famulari
2021-04-14 0:14 ` Bone Baboon [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=877dl5n2mb.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).