From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 25952@debbugs.gnu.org, contact.ng0@cryptolab.net
Subject: bug#25952: offloading empty machines file
Date: Mon, 25 May 2020 22:32:11 +0200 [thread overview]
Message-ID: <87tv03ycvo.fsf@nckx> (raw)
In-Reply-To: <CAJ3okZ2789hrEjvDX2Tsp84tnJgTa4fGP0DR+wfsUEVKCi21bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Simon,
zimoun 写道：
> This bug [1] had not been commented since the last 3 years and
> it has
> been asked more info 3 weeks ago.
The issue is that files such as /etc/guix/machines.scm (but this
applies equally to /etc/guix/acl & so on) are expected to evaluate
to a sexp.
An empty file does not a valid sexp make, so Guix throws an
prickly backtrace @ your face & dies. This is unlike most other
configuration formats where an empty file or one consisting
entirely of comments is a no-op.
We should decide whether ‘’ is a valid sexp (oh dear, philosophy)
or throw something softer at people.
> Therefore, I am closing. Feel free to reopen if I misunderstand
> something.
I think this bug should remain open until it's decided. What you?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-25 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:56 bug#25952: offloading: empty machines file leads to error ng0
2020-05-03 16:43 ` bug#25952: offloading empty machines file zimoun
2020-05-25 17:12 ` zimoun
2020-05-25 20:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-05-25 22:43 ` zimoun
2020-09-14 17:26 ` zimoun
2021-07-05 11:07 ` bug#25952: offloading: empty machines file leads to error zimoun
2021-07-13 8:11 ` bug#25952: offloading empty machines file zimoun
2021-08-18 1:24 ` bug#25952: offloading: empty machines file leads to error Maxim Cournoyer
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=87tv03ycvo.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=25952@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
--cc=me@tobias.gr \
--cc=zimon.toutoune@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.
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).