From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: lua54-luasocket-3.1.0
Date: Fri, 28 Apr 2023 03:53:31 +0200 [thread overview]
Message-ID: <20230428015331.j2MJDdbMYAvKvb3HhAIBpCdaRZSufDnG0ML4FTSUVj8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41608@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
There's a closed pull request on the void-packages repository
New package: lua54-luasocket-3.1.0
https://github.com/void-linux/void-packages/pull/41608
Description:
This is derived from lua51-luasocket but without the transitional package luasocket, and from the new upstream (hence the different version).
This version is required to update the prosody package to use lua54 instead of the now-deprecated lua51.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- ppc
prev parent reply other threads:[~2023-04-28 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 20:30 [PR PATCH] " linkmauve
2023-04-14 1:50 ` github-actions
2023-04-28 1:53 ` 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=20230428015331.j2MJDdbMYAvKvb3HhAIBpCdaRZSufDnG0ML4FTSUVj8@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).