GNU bug report logs - #66659
(home-)on-first-login script broken when no gexps are added

Previous Next

Package: guix;

Reported by: Nils Landt <nils <at> landt.email>

Date: Sat, 21 Oct 2023 06:15:01 UTC

Severity: normal

Done: Clément Lassieur <clement <at> lassieur.org>

Bug is archived. No further changes may be made.

Full log


Message #35 received at 66659 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Nils Landt <nils <at> landt.email>, Rostislav Svoboda
 <rostislav.svoboda <at> gmail.com>, Clément Lassieur
 <clement <at> lassieur.org>
Cc: 66659 <at> debbugs.gnu.org
Subject: Re: bug#66659: (home-)on-first-login script broken when no gexps
 are added
Date: Sat, 28 Oct 2023 00:22:29 +0200
Hi,

Nils Landt <nils <at> landt.email> skribis:

> 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)"

Oops, my bad.  (I did check at the REPL that (begin) was fine but forgot
that I was checking the top-level ‘begin’ form, which is not the same as
the sequencing ‘begin’ form…)

Rostislav Svoboda <rostislav.svoboda <at> gmail.com> skribis:

> Adding *unspecified* works for me. I.e.:
>
>     (when (claim-first-run flag-file-path)
>       ;; GEXPS can be empty, hence 'begin *unspecified*'. Having just
>       ;; 'begin' without '*unspecified*' leads to
>       ;; "Syntax error: ... sequence of zero expressions in form (begin)"
>       (begin *unspecified* #$@gexps))
>
> The patch is in the attachment.

Thanks Rostislav and everyone, and apologies for not replying earlier!

Ludo’.




This bug report was last modified 1 year and 209 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.