From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Haunt 0.2.6 released
Date: Mon, 7 Feb 2022 15:02:52 +0100 [thread overview]
Message-ID: <20220207140252.3bek3bj7wxfqyq4x@pelzflorian.localdomain> (raw)
In-Reply-To: <CAJ=RwfYUBXopB_BBV_AXhMcMk1bypCg9BzPk7e1gdWcF8k40sA@mail.gmail.com>
Hi David and thank you for the new Haunt release.
On Wed, Jan 26, 2022 at 08:26:19AM -0500, Thompson, David wrote:
> Haunt version 0.2.6 has been released. This release restores
> compatibility with Guile < 3.0 that was accidentally broken in 0.2.5.
You need not care about it on old Guile IMHO, but in case you do,
check is buggy now.
guix shell --container -D guile2.2-haunt autoconf automake
./bootstrap
./configure
make
make check
The problem is that tests/helper.scm’s test-end returns unspecified.
This also breaks the check for haunt-0.2.6 on Parabola GNU/Linux-libre.
This seems to be a bug in Guile’s SRFI-64 implementation, fixed with
the later Guile commit f10bc1a86. If I change Guix to use a patch of
the first hunk of that commit for Guile@2.2.7, it works.
Note that
guix build guile2.2-haunt \
--with-source=guile2.2-haunt='https://files.dthompson.us/haunt/haunt-0.2.6.tar.gz'
does not run tests at all according to its log file. Neither does
guix build haunt.
Sorry for reporting this late.
Regards,
Florian
next prev parent reply other threads:[~2022-02-07 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 13:26 Haunt 0.2.6 released Thompson, David
2022-02-07 14:02 ` pelzflorian (Florian Pelz) [this message]
2022-02-07 14:06 ` [EXT] " Thompson, David
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=20220207140252.3bek3bj7wxfqyq4x@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=dthompson2@worcester.edu \
--cc=guile-user@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).