From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Bavier Subject: bug#37965: parse-error in latest news entry Date: Mon, 28 Oct 2019 12:57:48 -0400 (EDT) Message-ID: <564677810.293420.1572281868245.JavaMail.zimbra@centurylink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44717) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iP8LE-0001EK-3j for bug-guix@gnu.org; Mon, 28 Oct 2019 12:58:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iP8LC-0005oy-PP for bug-guix@gnu.org; Mon, 28 Oct 2019 12:58:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37473) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iP8LC-0005oo-Li for bug-guix@gnu.org; Mon, 28 Oct 2019 12:58:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iP8LC-0006fc-Ip for bug-guix@gnu.org; Mon, 28 Oct 2019 12:58:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:44693) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iP8L1-0000zj-Fk for bug-guix@gnu.org; Mon, 28 Oct 2019 12:57:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iP8L0-0005bS-1G for bug-guix@gnu.org; Mon, 28 Oct 2019 12:57:51 -0400 Received: from mail.onyx.syn-alias.com ([206.152.134.66]:7030 helo=smtp.centurylink.net) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iP8Kz-0005ap-RM for bug-guix@gnu.org; Mon, 28 Oct 2019 12:57:49 -0400 List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 37965@debbugs.gnu.org Commit https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3Db13b9384bc43= bf93c754c037956c8ef9a99c2b41 causes a recent 'guix pull' to throw a parse-e= rror: News for channel 'guix' Backtrace: 16 (apply-smob/1 #) In ice-9/boot-9.scm: 705:2 15 (call-with-prompt _ _ #) In ice-9/eval.scm: 619:8 14 (_ #(#(#))) In guix/ui.scm: 1730:12 13 (run-guix-command _ . _) In ice-9/boot-9.scm: 829:9 12 (catch _ _ # =E2=80=A6) 829:9 11 (catch _ _ # =E2=80=A6) 829:9 10 (catch _ _ # =E2=80=A6) In srfi/srfi-1.scm: 640:9 9 (for-each # =E2=80=A6) In guix/scripts/pull.scm: 283:11 8 (display-channel-specific-news _ _ #:port _ #:concise? _) In srfi/srfi-1.scm: 640:9 7 (for-each # =E2=80=A6) In guix/scripts/pull.scm: 251:2 6 (display-news-entry #< commit: "49=E2=80= =A6> =E2=80=A6) 241:12 5 (display-news-entry-title _ _ #) In guix/ui.scm: 1210:23 4 (texi->plain-text _) In texinfo.scm: 1131:22 3 (parse _) 979:31 2 (loop # (*fragment*) _ _ _) 910:31 1 (loop # #f # =E2=80=A6) 745:27 0 (_ # #f #f # =E2=80=A6) texinfo.scm:745:27: Throw to key `parser-error' with args `(# "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 b= e code and can cause errors for users like this? './pre-inst-env guix pull= --news' seems to still read news ~/.config/guix/current. --=20 `~Eric