unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 41336-done@debbugs.gnu.org
Subject: bug#41336: guix pull error (on armhf) a few minutes ago
Date: Mon, 19 Oct 2020 08:59:48 -0400	[thread overview]
Message-ID: <87imb65q2j.fsf@gmail.com> (raw)
In-Reply-To: <20200516221731.2f67ef92@scratchpost.org> (Danny Milosavljevic's message of "Sat, 16 May 2020 22:17:31 +0200")

Hello Danny,

Danny Milosavljevic <dannym@scratchpost.org> writes:

> ./guix.ru.texi:956: warning: accent command `@,' must not be followed by whitespace
> ./guix.ru.texi:21275: @pxref reference to nonexistent node `Channels'
> ./guix.ru.texi:26842: @pxref reference to nonexistent node `Channels'
> ./guix.ru.texi:28006: @pxref reference to nonexistent node `Channels'
> Backtrace:
>            3 (primitive-load "/gnu/store/jgy520477c1wis3cx9rsq6pzvh7?")
> In ice-9/eval.scm:
>     619:8  2 (_ #f)
> In ice-9/boot-9.scm:
>    260:13  1 (for-each #<procedure 2e70c0 at ice-9/eval.scm:333:13 ?> ?)
> In guix/build/utils.scm:
>     654:6  0 (invoke _ . _)
>
> guix/build/utils.scm:654:6: In procedure invoke:
> ERROR:
>   1. &invoke-error:
>       program: "/gnu/store/cd9vnmj0z9068xrgvssavnkfc8a9svly-texinfo-6.7/bin/makeinfo"
>       arguments: ("./guix.ru.texi" "-I" "/gnu/store/mq3nc6nas9p2ws259lx61vsyfgckmwpb-doc" "-I" "." "-o" "/gnu/store/bd9xg07n7jc5bf2x3afhr6k80v4biykg-guix-manual/guix.ru.info")
>       exit-status: 1
>       term-signal: #f
>       stop-signal: #f

I've 'guix environment --system=armhf-linux guix' into my checkout, then
ran:

--8<---------------cut here---------------start------------->8---
$ for i in {1..20}; do if ! makeinfo -v guix.ru.texi -I .; \
  then echo "error: makeinfo exited with $?"; break; fi; done
guix.ru.texi:968: warning: accent command `@,' must not be followed by whitespace
Output file guix.ru.info
Renaming first output file as guix.ru.info-1
New output file guix.ru.info-2
New output file guix.ru.info-3
New output file guix.ru.info-4
New output file guix.ru.info-5
Outputing the split manual file guix.ru.info
Wide character in warn at /gnu/store/r5j8yxxf7sknj3bqpfw2qwq30awhzakb-profile/bin/makeinfo line 632.
guix.ru.texi:4239: warning: `.' or `,' must follow @xref, not д
guix.ru.texi:968: warning: accent command `@,' must not be followed by whitespace
--8<---------------cut here---------------end--------------->8---

without encountering the above problem.

Closing, but feel free to reopen if you encounter it again or are able
to reproduce it.

Thanks,

Maxim




      reply	other threads:[~2020-10-19 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 20:17 bug#41336: guix pull error (on armhf) a few minutes ago Danny Milosavljevic
2020-10-19 12:59 ` Maxim Cournoyer [this message]

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=87imb65q2j.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=41336-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).