From: Eric Bavier <ericbavier@centurylink.net>
To: 37965@debbugs.gnu.org
Subject: bug#37965: parse-error in latest news entry
Date: Mon, 28 Oct 2019 12:57:48 -0400 (EDT) [thread overview]
Message-ID: <564677810.293420.1572281868245.JavaMail.zimbra@centurylink.net> (raw)
Commit https://git.savannah.gnu.org/cgit/guix.git/commit/?id=b13b9384bc43bf93c754c037956c8ef9a99c2b41 causes a recent 'guix pull' to throw a parse-error:
News for channel 'guix'
Backtrace:
16 (apply-smob/1 #<catch-closure 7f64e679a200>)
In ice-9/boot-9.scm:
705:2 15 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
619:8 14 (_ #(#(#<directory (guile-user) 7f64e644b140>)))
In guix/ui.scm:
1730:12 13 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 12 (catch _ _ #<procedure 7f64e63bb018 at guix/ui.scm:642…> …)
829:9 11 (catch _ _ #<procedure 7f64e63bb030 at guix/ui.scm:765…> …)
829:9 10 (catch _ _ #<procedure 7f64e3d27878 at guix/scripts/pu…> …)
In srfi/srfi-1.scm:
640:9 9 (for-each #<procedure 7f64e3d256e0 at guix/scripts/pul…> …)
In guix/scripts/pull.scm:
283:11 8 (display-channel-specific-news _ _ #:port _ #:concise? _)
In srfi/srfi-1.scm:
640:9 7 (for-each #<procedure 7f64d5b03720 at guix/scripts/pul…> …)
In guix/scripts/pull.scm:
251:2 6 (display-news-entry #<<channel-news-entry> commit: "49…> …)
241:12 5 (display-news-entry-title _ _ #<output: file /dev/pts/19>)
In guix/ui.scm:
1210:23 4 (texi->plain-text _)
In texinfo.scm:
1131:22 3 (parse _)
979:31 2 (loop #<input: string 7f64e6483230> (*fragment*) _ _ _)
910:31 1 (loop #<input: string 7f64e6483230> #f #<procedure ide…> …)
745:27 0 (_ #<input: string 7f64e6483230> #f #f #<procedure 7f6…> …)
texinfo.scm:745:27: Throw to key `parser-error' with args `(#<input: string 7f64e6483230> "EOF while reading a token " "reading char data")'
I believe this is due to missing trailing '}' in the en title:
(entry (commit "49af34cfac89d384c46269bfd9388b2c73b1220a")
(title (en "@command{guix pull} now honors
@file{/etc/guix/channels.scm")
^
BTW, is there a good way to test these news entries, since they appear to be code and can cause errors for users like this? './pre-inst-env guix pull --news' seems to still read news ~/.config/guix/current.
--
`~Eric
next reply other threads:[~2019-10-28 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 16:57 Eric Bavier [this message]
[not found] ` <handler.37965.B.157228187825626.ack@debbugs.gnu.org>
2019-10-28 20:27 ` bug#37965: parse-error in latest news entry Eric Bavier
2019-10-28 20:59 ` Eric Bavier
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=564677810.293420.1572281868245.JavaMail.zimbra@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=37965@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).