From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 25952@debbugs.gnu.org, contact.ng0@cryptolab.net
Subject: bug#25952: offloading: empty machines file leads to error
Date: Mon, 05 Jul 2021 13:07:05 +0200 [thread overview]
Message-ID: <87wnq5j9ye.fsf_-_@gmail.com> (raw)
In-Reply-To: <87k0wwqng4.fsf@gmail.com> (zimoun's message of "Mon, 14 Sep 2020 19:26:35 +0200")
Hi,
For reference: <http://issues.guix.gnu.org/issue/25952>.
On Mon, 14 Sep 2020 at 19:26, zimoun <zimon.toutoune@gmail.com> wrote:
> On Tue, 26 May 2020 at 00:43, zimoun <zimon.toutoune@gmail.com> wrote:
>> On Mon, 25 May 2020 at 22:32, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>>
>>> 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.
>>
>> Hum? I am not sure to get the point. Are we talking about this kind
>> of situations, e.g.,
>>
>> touch /tmp/empty.scm
>> guix package -m /tmp/empty.scm -p /tmp/empy
>>
>> or
>>
>> echo ";; hello" > /tmp/comment.scm
>> guix package -m /tmp/comment.scm -p /tmp/comment
>>
>> or
>>
>> echo "(define x 42)" > /tmp/answer.scm
>> guix package -m /tmp/answer.scm -p /tmp/answer
>>
>>
>> ?
>
> If we are talking about such cases, I think we can close this bug
> report.
>
>
>>> We should decide whether ‘’ is a valid sexp (oh dear, philosophy)
>>> or throw something softer at people.
>>
>> Throw something more "helping" than e.g.,
>>
>> Backtrace:
>> 1 (primitive-load "/home/simon/.config/guix/current/bin/g…")
>> In guix/ui.scm:
>> 1936:12 0 (run-guix-command _ . _)
>>
>> guix/ui.scm:1936:12: In procedure run-guix-command:
>> In procedure struct-vtable: Wrong type argument in position 1
>> (expecting struct): #<unspecified>
>>
>> ?
>
> More helping as suggested for example in this message:
>
> <https://lists.gnu.org/archive/html/guix-devel/2020-09/msg00125.html>
>
> If yes, the bug report should be renamed. And probably goes to the
> Guile bug tracker. :-)
What do we do? What is the next action? Close? If not, please provide
explanations about what the issue really is and what could be the plan
to fix it. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-07-05 11:10 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
2020-05-25 22:43 ` zimoun
2020-09-14 17:26 ` zimoun
2021-07-05 11:07 ` zimoun [this message]
2021-07-13 8:11 ` 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=87wnq5j9ye.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=25952@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
--cc=me@tobias.gr \
/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).