From: Mark H Weaver <mhw@netris.org>
To: Svante Signell <svante.signell@gmail.com>
Cc: 37037-done@debbugs.gnu.org
Subject: bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.
Date: Fri, 23 Aug 2019 15:23:21 -0400 [thread overview]
Message-ID: <87v9unvg6z.fsf@netris.org> (raw)
In-Reply-To: <e0df178d9e042cdc04eae894901bd20a8eaf5e20.camel@gmail.com> (Svante Signell's message of "Fri, 23 Aug 2019 13:16:46 +0200")
Svante Signell <svante.signell@gmail.com> writes:
> On Thu, 2019-08-22 at 17:01 -0400, Mark H Weaver wrote:
>> It looks like this issue was already fixed in Guile 2.0.14, by commit
>> f2764cb1031379c47a17c02fef3f8164a6ce9cda on the 'stable-2.0' branch:
>>
>> https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=f2764cb1031379c47a17c02fef3f8164a6ce9cda
>>
>> Would you like to try it and report back?
>
> Thank you, that commit fixed the problem. Reported to Debian version
> 2.0.13+1-5.1 as bug #935505, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935505
Great, thanks for letting us know. I'm closing this bug now.
Regards,
Mark
prev parent reply other threads:[~2019-08-23 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 12:29 bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test Svante Signell
2019-08-22 18:33 ` Svante Signell
2019-08-22 18:34 ` bug#37037: [Fwd: Re: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.] Svante Signell
2019-08-22 21:01 ` bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test Mark H Weaver
2019-08-23 11:16 ` Svante Signell
2019-08-23 19:23 ` Mark H Weaver [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://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=87v9unvg6z.fsf@netris.org \
--to=mhw@netris.org \
--cc=37037-done@debbugs.gnu.org \
--cc=svante.signell@gmail.com \
/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).