unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
	Jesse Gibbons <jgibbons2357@gmail.com>,
	37347@debbugs.gnu.org
Subject: bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page
Date: Thu, 3 Oct 2019 18:39:45 +0200	[thread overview]
Message-ID: <20191003183945.2397bacf@kompiuter> (raw)
In-Reply-To: <87tv9c5iyn.fsf@gnu.org>

On Mon, 16 Sep 2019 18:01:04 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> It looks like X.509 certificates used to authenticate web sites over
> HTTPS could not be found.
> 
> Did you set environment variables and all as described at
> <https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html>?
> 
> HTH,
> Ludo’.

Hi again, I've tried setting these variables in the environment but the
same effect. How can I get "guix refresh" to work in the environment?
I think this should be explained somewhere a bit more, because after
reading the packaging tutorial and parts of the documentation I
couldn't set up the development environment for Guix. 
A simple step-by-step tutorial or just list of things to do would make
it more understandable.
Is this already work in progress in the Cookbook?

For example in this section:
https://guix.gnu.org/manual/en/html_node/Building-from-Git.html#Building-from-Git

It is easy to miss the last step - running "make check", because it
isn't explained that running "make check" is necessary to be able to
run ./pre-inst-env. I thought I could just skip this and start hacking.

It would be more clear if the manual or the cookbook contained a
step-by-step list like this:

Quick setting up the environment:
1. git clone ...
2. ./bootstrap
3. ./configure --localstatedir=/var/
4. make check
5. setting certificates to be able to update a package
etc.


Jan Wielkiewicz

  parent reply	other threads:[~2019-10-03 16:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  0:49 bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page Jan
2019-09-09  1:14 ` Jesse Gibbons
2019-09-09  6:23   ` Julien Lepiller
2019-09-11 20:53     ` Jan
2019-09-16 16:01       ` Ludovic Courtès
2019-09-16 17:40         ` Jan
2019-10-03 16:39         ` Jan Wielkiewicz [this message]
2019-10-03 19:57         ` Bengt Richter
2019-10-04  3:06           ` Bengt Richter
2019-10-04  7:15             ` Jelle Licht
2019-10-04 22:27               ` Bengt Richter
2019-10-05 12:58                 ` Marius Bakke
2019-10-06 19:00         ` Jan Wielkiewicz
2019-10-24 20:16 ` Gábor Boskovits

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=20191003183945.2397bacf@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=37347@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    --cc=julien@lepiller.eu \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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