From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: haunt-0.2.4
Date: Wed, 25 May 2022 04:14:45 +0200 [thread overview]
Message-ID: <20220525021445.AQP5HxcBC0HLg4RE2T2MXPbniG8D5zBXBeFRw6vuIkQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29694@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
There's a closed pull request on the void-packages repository
New package: haunt-0.2.4
https://github.com/void-linux/void-packages/pull/29694
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
Building guile-reader appears to fail on non-native architectures. I do not understand why, whether it can be fixed in the template or if its an upstream bug. There appears to have been some mailing list discussion about this some years ago [here](https://lists.gnu.org/archive/html/guile-reader-devel/2017-11/threads.html). Advice is appreciated.
```
checking for scm_take_u8vector... no
configure: error: You need Guile 1.8.x or higher.
=> ERROR: guile-reader-0.6.3_1: do_configure: '${configure_script} ${configure_args}' exited with 1
=> ERROR: in do_configure() at common/build-style/gnu-configure.sh:8
```
prev parent reply other threads:[~2022-05-25 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 3:31 [PR PATCH] Haunt aliasless
2022-05-11 2:12 ` New package: haunt-0.2.4 github-actions
2022-05-25 2:14 ` github-actions [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220525021445.AQP5HxcBC0HLg4RE2T2MXPbniG8D5zBXBeFRw6vuIkQ@z \
--to=ml@inbox.vuxu.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 NNTP newsgroup(s).