From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: 40809@debbugs.gnu.org
Subject: bug#40809: Apology: documentation for srfi-modules broken?
Date: Fri, 24 Apr 2020 09:07:26 +0200 [thread overview]
Message-ID: <8a8fa7a5-8766-4721-9cdd-564dc9b3a1c8@www.fastmail.com> (raw)
Hello Guilers!
I submitted my patch for srfi-171 which got merged. I built it (or rather: I believe I did) on my little arm board without issues. However, after finally getting some computer time yesterday I tried to build guile master on my Mac, and when I checked the terminal window quickly this morning there was a build failure due to errors in srfi-modules.texi. I built it through homebrew, so those the verbosity was on -11, so all I could see was stderr.
The warning I got was on Line 5767: @var{(reader)} should be @var{reader} (I only had about 30s this morning. There were other warnings, but I think they weren't related to my patch, so I didn't really remember them.
The error was a space between @result and {} on line 6013.
This did not seem to affect the release of 3.0.2, but if the output of the homebrew install (using my own recipe to properly build from master) is to be believed I managed to break making the documentation (or maybe homebrew is picky).
I won't have any computer access for a week or two, so I'll have to bear my shame publicly on the mailing list; if anyone could have a look I would be very thankful.
As I said, I didn't have any time to do diagnostics, but if somebody else got bitten by this I am very sorry. If anything it has taught me to not make patches over a cell phone SSH session to an SBC.
I will correct this as soon as I have computer access again if nobody else does it first.
Best regards from Sweden
Linus Björnstam
reply other threads:[~2020-04-24 7:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a8fa7a5-8766-4721-9cdd-564dc9b3a1c8@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=40809@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.
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).