From: Nils Landt <nils@landt.email>
To: 66659@debbugs.gnu.org
Subject: bug#66659: closed (Re: bug#66659: (home-)on-first-login script broken when no gexps are added)
Date: Tue, 24 Oct 2023 12:05:41 +0200 (CEST) [thread overview]
Message-ID: <1963527562.259546.1698141941111@office.mailbox.org> (raw)
In-Reply-To: <handler.66659.D66659.169789774918233.notifdone@debbugs.gnu.org>
> help-debbugs@gnu.org hat am 21.10.2023 16:16 CEST geschrieben:
>
>
> Your bug report
>
> #66659: (home-)on-first-login script broken when no gexps are added
>
> which was filed against the guix package, has been closed.
>
> The explanation is attached below, along with your original report.
> If you require more details, please reply to 66659@debbugs.gnu.org.
>
> --
> 66659: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66659
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
> Hi Carlo & Nils,
>
> I’ve just pushed something similar to what you provided, Carlo, in
> commit e098ba2f499bbddfea50c85058e4077e39b85513.
>
> We should be good now.
I'm afraid this did not fix the issue. It results in
(when (claim-first-run flag-file-path) (begin))
which leads to the new error message "Syntax error:
/home/nl/.guix-home/on-first-login:3:1272: sequence of zero expressions in form (begin)"
next prev parent reply other threads:[~2023-10-24 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 6:14 bug#66659: (home-)on-first-login script broken when no gexps are added Nils Landt
2023-10-21 9:27 ` Carlo Zancanaro
2023-10-21 9:39 ` bug#66659: [PATCH] home: services: Don't crash on-first-login when nothing to do Carlo Zancanaro
2023-10-21 14:15 ` bug#66659: (home-)on-first-login script broken when no gexps are added Ludovic Courtès
[not found] ` <handler.66659.D66659.169789774918233.notifdone@debbugs.gnu.org>
2023-10-24 10:05 ` Nils Landt [this message]
2023-10-24 23:19 ` Clément Lassieur
2023-10-27 22:22 ` Ludovic Courtès
2023-10-24 14:17 ` Rostislav Svoboda
2023-10-27 14:53 ` Clément Lassieur
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=1963527562.259546.1698141941111@office.mailbox.org \
--to=nils@landt.email \
--cc=66659@debbugs.gnu.org \
/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).