From: Csepp <raingloom@riseup.net>
To: jgart <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: fatal empty ident name (for <>) not allowed
Date: Sat, 12 Nov 2022 13:09:46 +0100 [thread overview]
Message-ID: <87bkpcz842.fsf@riseup.net> (raw)
In-Reply-To: <20221111074137.GB1672@dismail.de>
jgart <jgart@dismail.de> writes:
> Does anyone happen to know what this error is about?
>
> Applying: * gnu/packages/lisp.scm (carp): New variable.
> fatal: empty ident name (for <>) not allowed
>
> It happens when I try to apply v8 of this patch:
>
> https://issues.guix.gnu.org/58898#9
The <> makes me think of the '(ice-9 cut) module but I haven't seen this
error.
next prev parent reply other threads:[~2022-11-12 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:41 fatal empty ident name (for <>) not allowed jgart
2022-11-12 12:09 ` Csepp [this message]
2022-11-12 13:19 ` Ricardo Wurmus
2022-11-12 13:38 ` jgart
2022-11-12 14:05 ` Ricardo Wurmus
2022-11-12 14:38 ` jgart
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=87bkpcz842.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.
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).