unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35541@debbugs.gnu.org
Subject: bug#35541: Installer does not add %base-packages
Date: Sat, 04 May 2019 14:40:30 +0200	[thread overview]
Message-ID: <87tvea4cld.fsf@gnu.org> (raw)
In-Reply-To: <87muk3da0e.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 03 May 2019 13:59:13 +0200")

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Hello,

Ludovic Courtès <ludo@gnu.org> skribis:

> I think we should email info-guix@gnu.org and possibly write a post on
> the blog within at most two days with an explanation of the issue,
> workarounds, proper fix (which is to edit the config file and
> reconfigure), and an ETA for the bug-fix release.

Unless there are objections, I will apply the patch below to the manual
in the ‘version-1.0.0’ branch and update the on-line copies of the
manual.  That way the issue and workaround should be immediately visible
to someone who follows the “Installation instructions” link on the
download page.  (This text won’t be translated, but we’ll have to live
with it I guess.)

I’ll also send roughly the same text to info-guix.

Please tell me what you think!

I think we can publish a release in two to four weeks.  It should be an
easier one anyway.  We should take advantage of that time to gather
installation bug reports and to address them, and also to see how we can
automate the release process further.

Thoughts?

Thanks,
Ludo’.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 2460 bytes --]

diff --git a/doc/guix.texi b/doc/guix.texi
index 3b0517c5e3..2f1caf4659 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1774,6 +1774,11 @@ on a machine.  Guix, as a package manager, can
 also be installed on top of a running GNU/Linux system,
 @pxref{Installation}.
 
+@quotation Important Note
+@xref{Guided Graphical Installation}, on how to work around a bug that affects
+the graphical installer in version 1.0.0.
+@end quotation
+
 @ifinfo
 @quotation Note
 @c This paragraph is for people reading this from tty2 of the
@@ -1992,6 +1997,56 @@ dependencies of your system configuration can be downloaded.  See the
 The graphical installer is a text-based user interface.  It will guide you,
 with dialog boxes, through the steps needed to install GNU@tie{}Guix System.
 
+@quotation Important Note
+Due to a @uref{https://issues.guix.info/issue/35541, bug}, the graphical
+installer of Guix 1.0.0 may produce a system configuration where essential
+commands such as @command{ls} or @command{grep} are missing.  A new release
+will be published in the coming weeks.  Here is how you can work around it in
+the meantime on your freshly installed system:
+
+@itemize
+@item
+Install packages that provide those commands, along with the text editor of
+your choice (for example, @code{emacs} or @code{vim}):
+
+@example
+guix install coreutils findutils grep procps sed emacs vim
+@end example
+
+At this point, the essential commands you would expect are available.
+
+@item
+Open your configuration file with your editor of choice, for example
+@command{emacs}, running as root:
+
+@example
+sudo emacs /etc/config.scm
+@end example
+
+@item
+Change the @code{packages} field to add the ``base packages'' to the list of
+globally-installed packages, such that your configuration looks like this:
+
+@lisp
+(operating-system
+  ;; ... snip ...
+  (packages (append (list (specification->package "nss-certs"))
+                    %base-packages))
+  ;; ... snip ...
+  )
+@end lisp
+
+@item
+Reconfigure the system so that your new configuration is in effect:
+
+@example
+sudo guix system reconfigure /etc/config.scm
+@end example
+@end itemize
+
+We apologize for this embarrassing mistake that we made.
+@end quotation
+
 The first dialog boxes allow you to set up the system as you use it during the
 installation: you can choose the language, keyboard layout, and set up
 networking, which will be used during the installation.  The image below shows

  parent reply	other threads:[~2019-05-04 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03  8:56 bug#35541: Installer does not add %base-packages pelzflorian (Florian Pelz)
2019-05-03 10:08 ` Ludovic Courtès
2019-05-03 10:26   ` Ricardo Wurmus
2019-05-03 11:59     ` Ludovic Courtès
2019-05-03 16:08       ` Timothy Sample
2019-05-03 18:42         ` Timothy Sample
2019-05-03 19:19         ` Ludovic Courtès
2019-05-03 20:39           ` Timothy Sample
2019-05-04 12:40       ` Ludovic Courtès [this message]
2019-05-04 13:32         ` pelzflorian (Florian Pelz)
2019-05-04 14:54           ` Ludovic Courtès
2019-05-04 15:03             ` pelzflorian (Florian Pelz)
2019-05-04 21:16               ` Ludovic Courtès
2019-05-04 16:49         ` Ricardo Wurmus
2019-05-03 10:30   ` Ludovic Courtès
2019-05-03 11:52 ` Ludovic Courtès

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=87tvea4cld.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35541@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).