unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: guix pull error after install i686 1.2.0
Date: Sun, 11 Apr 2021 15:04:14 -0400	[thread overview]
Message-ID: <YHNILpuS7TAmzjtN@jasmine.lan> (raw)
In-Reply-To: <87tuodegc5.fsf@disroot.org>

On Sat, Apr 10, 2021 at 09:54:18PM -0400, Bone Baboon wrote:
> I can reproduce this after two separate install using this install
> image: 
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.2.0.i686-linux.iso.xz

Okay. I have installed this ISO in a virtual machine, following the
instructions in the manual section Installing Guix in a VM.

> The output of `guix pull`:
> ```
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
> guix pull: error: Git error: the SSL certificate is invalid
> ```

I logged in as a regular user, ran `guix pull`, and it completed
successfully. I also tried as root, and that worked too.

> I am running `guix pull` from a Linux console virtual terminal.
> I am running `guix pull` as a regular user (not root).

Okay.

> `which guix` outputs "/run/current-system/profile/bin/guix".

Okay.

> 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.


  reply	other threads:[~2021-04-11 19:04 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 [this message]
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

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=YHNILpuS7TAmzjtN@jasmine.lan \
    --to=leo@famulari.name \
    --cc=bone.baboon@disroot.org \
    --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).