From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: crystal-1.0.0
Date: Wed, 19 Oct 2022 04:14:14 +0200 [thread overview]
Message-ID: <20221019021414.EzbYVWM8u9m-2z2mo73ZE5ScnhEWdzbKXOlMFa1Am5A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30019@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
There's a closed pull request on the void-packages repository
New package: crystal-1.0.0
https://github.com/void-linux/void-packages/pull/30019
Description:
#### 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Extra info
- upgrade to llvm11
- use openssl
- re-enabled do_check()
#### Archs
- I built this PR locally for these architectures with -Q:
- [x] i686-glibc with -Q
- [x] x86_64-glibc with -Q
- [x] x86_64-musl with -Q
Were not able to test the ARM platforms
next prev parent reply other threads:[~2022-10-19 2:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 15:07 [PR PATCH] srcpkgs/crystal: update to 1.0.0 mipmip
2021-04-05 15:10 ` ericonr
2021-04-05 15:10 ` [PR REVIEW] " ericonr
2021-04-05 15:16 ` [PR PATCH] [Updated] " mipmip
2021-04-05 15:18 ` [PR REVIEW] " mipmip
2021-07-07 9:14 ` New package: crystal-1.0.0 mfiano
2021-09-11 13:48 ` notramo
2021-09-11 13:48 ` notramo
2022-03-30 5:46 ` notramo
2022-04-01 9:45 ` mipmip
2022-07-01 2:14 ` github-actions
2022-07-05 12:30 ` notramo
2022-10-05 2:13 ` github-actions
2022-10-19 2:14 ` github-actions [this message]
2022-10-19 10:46 ` notramo
2022-10-19 10:49 ` paper42
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=20221019021414.EzbYVWM8u9m-2z2mo73ZE5ScnhEWdzbKXOlMFa1Am5A@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).