From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35541@debbugs.gnu.org
Subject: bug#35541: Installer does not add %base-packages
Date: Fri, 03 May 2019 12:30:46 +0200 [thread overview]
Message-ID: <874l6beso9.fsf@gnu.org> (raw)
In-Reply-To: <87imuretpb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 03 May 2019 12:08:32 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
>> When and only when the Newt installer creates a packages field in the
>> operating-system configuration e.g. for nss-certs, it does not add
>> %base-packages to the packages field. (When no packages field is
>> created, %base-packages is added by default.)
>
> Ouch! That renders the installed system unusable, right?
I did a full install for a bare-bones-like system with ‘nss-certs’
selected during the install. The resulting system has only ‘guix’ and
‘herd’ as useful commands in /run/current-system/profile/bin.
You can log in but Coreutils commands etc. are missing. You can run:
guix install coreutils grep sed findutils
which solves the problem.
It’s a serious issue nonetheless. :-/
Ludo’.
next prev parent reply other threads:[~2019-05-03 10:31 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
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 [this message]
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=874l6beso9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35541@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).