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: Fri, 03 May 2019 13:59:13 +0200 [thread overview]
Message-ID: <87muk3da0e.fsf@gnu.org> (raw)
In-Reply-To: <87ftpvhm11.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 03 May 2019 12:26:02 +0200")
Hello,
I’d like us to better estimate the impact, communicate about
workarounds, and have a bug-fix release plan.
Like I wrote, in a bare-bones installation, Coreutils & co. are missing,
but one can work around it by running, say:
guix install coreutils grep sed findutils
(Programs like ‘sudo’ and ‘passwd’ are available despite the bug because
they are in /run/setuid-programs.)
Has anyone tried on a GNOME, Xfce, or ratpoison install? I wonder if
the problem is visible there (until you open a terminal, that is.)
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.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2019-05-03 12:00 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 [this message]
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
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=87muk3da0e.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).