GNU bug report logs - #40809
Apology: documentation for srfi-modules broken?

Previous Next

Package: guile;

Reported by: Linus Björnstam <linus.bjornstam <at> veryfast.biz>

Date: Fri, 24 Apr 2020 07:21:03 UTC

Severity: minor

To reply to this bug, email your comments to 40809 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guile <at> gnu.org:
bug#40809; Package guile. (Fri, 24 Apr 2020 07:21:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Linus Björnstam <linus.bjornstam <at> veryfast.biz>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Fri, 24 Apr 2020 07:21:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Linus Björnstam <linus.bjornstam <at> veryfast.biz>
To: bug-guile <at> gnu.org
Subject: Apology: documentation for srfi-modules broken?
Date: Fri, 24 Apr 2020 09:07:26 +0200
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




This bug report was last modified 4 years and 11 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.