From: Pierre Neidhardt <mail@ambrevar.xyz>
To: 42247@debbugs.gnu.org
Subject: bug#42247: Channel news raise error on `guix pull`
Date: Tue, 07 Jul 2020 16:54:22 +0200 [thread overview]
Message-ID: <875zaz2x5t.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
I've added a news-file entry to my channel:
--8<---------------cut here---------------start------------->8---
(channel
(version 0)
(news-file "news.scm"))
--8<---------------cut here---------------end--------------->8---
which contains
--8<---------------cut here---------------start------------->8---
(channel-news
(version 0)
(entry (commit "25387230a7f99c2b0886488ed061747c9e00434a")
(title (en "Hello"))
(body (en "World!"))))
--8<---------------cut here---------------end--------------->8---
Reading the news file from the REPL works.
--8<---------------cut here---------------start------------->8---
(with-input-from-file "/home/ambrevar/projects/foo/news.scm"
(lambda ()
(read-channel-news (current-input-port))))
--8<---------------cut here---------------end--------------->8---
However, guix pull chokes on it:
--8<---------------cut here---------------start------------->8---
(repl-version 0 0)
(exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (channel-news)) (value #f))
--8<---------------cut here---------------end--------------->8---
I first encountered this issue in Feb 2020, but this issue might have
been around since channel news were introduced.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2020-07-07 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 14:54 Pierre Neidhardt [this message]
2020-07-09 22:26 ` bug#42247: Channel news raise error on `guix pull` Ludovic Courtès
2020-07-11 9:13 ` Pierre Neidhardt
2020-07-13 10:27 ` Ludovic Courtès
2020-07-13 12:50 ` Bengt Richter
2020-07-14 8:53 ` Pierre Neidhardt
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=875zaz2x5t.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=42247@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).