unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull error after install i686 1.2.0
Date: Sat, 10 Apr 2021 16:12:11 -0400	[thread overview]
Message-ID: <87v98tew6c.fsf@disroot.org> (raw)
In-Reply-To: <CAEwRq=o4km-0P8Jb2pPsH7E_X=+_TDM0WrJmV_HrnsX=YH9uJA@mail.gmail.com>

Vincent Legoll writes:
> I remember having seen an (default checked) option
> to install certificates when choosing packages to install.

> I have the "nss-certs" package installed from /etc/config.scm
>
> This may be what you're missing.

I reinstalled Guix on the laptop.  During the graphical install I used
the default checked option for the certificates.  The only difference
with the install on this computer was that at the end when it prompts
for the install media to be removed and the reboot button used it went
to a blue screen and did not power off.  So I held the power button to
turn the computer off.

I was able to boot and sign in normally.  With a working Ethernet
connection `guix pull` gave the same error.  However `sudo guix system
reconfigure config.scm` worked fine and was able to download using the
internet connection.

`nss-certs` is in the system configuration file.

`locate certificates` shows that `etc/ssl/certs/ca-certificates.crt` is
in the store.

`ls /run/current-system/profile/etc/ssl/certs/ | wc --lines` outputs
301.


  reply	other threads:[~2021-04-10 20:12 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 [this message]
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

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=87v98tew6c.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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).