unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: new GuixSD version?
Date: Thu, 21 Jul 2016 13:35:01 +0200	[thread overview]
Message-ID: <87a8hbql5m.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=prrSkZfQ0fEu9mdH0NOGJRp_unCcevYtZ7sDYuX2CSfQ@mail.gmail.com> (Vincent Legoll's message of "Wed, 20 Jul 2016 16:13:13 +0200")

Vincent Legoll <vincent.legoll@gmail.com> skribis:

> Long story short:
>
> My first VM in which I installed guixsd successfully, didn't have enough
> disk space. So I decided to make a new one from scratch : Bad idea...

In the meantime, you could also generate your own up-to-date
installation image, which wouldn’t have this missing-substitute issue:

  https://www.gnu.org/software/guix/manual/html_node/Building-the-Installation-Image.html

> And as I'm a complete scheme newbie, I cannot make sense of the
> error messages I get, I cannot even know if PEBCAK...

Please report the confusing error messages.  We need to improve them,
but we need to know exactly what you see and what’s confusing about it!
Old farts like are too much brain-damaged to even realize that error
messages are confusing.  ;-)

Ludo’.

  reply	other threads:[~2016-07-21 11:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 21:36 new GuixSD version? Ethan Stefan Day
2016-07-20  3:55 ` Leo Famulari
2016-07-20  4:45   ` Ethan Stefan Day
2016-07-20  5:59     ` Leo Famulari
2016-07-20 13:34       ` Ludovic Courtès
2016-07-20 14:13         ` Vincent Legoll
2016-07-21 11:35           ` Ludovic Courtès [this message]
2016-07-21 11:44             ` Vincent Legoll
2016-07-21 12:00               ` Ludovic Courtès
2016-07-21 19:23       ` Ethan Stefan Day

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=87a8hbql5m.fsf@gnu.org \
    --to=ludo@gnu.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).