From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] coturn: update to 4.6.2.
Date: Mon, 10 Jul 2023 16:22:54 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44961@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
There is a new pull request by TinfoilSubmarine against master on the void-packages repository
https://github.com/TinfoilSubmarine/void-packages update/coturn
https://github.com/void-linux/void-packages/pull/44961
coturn: update to 4.6.2.
<!-- 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**|**NO**
-->
<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/44961.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/coturn-44961.patch --]
[-- Type: text/x-diff, Size: 1081 bytes --]
From 3a2c1a378969f21b8a46e5e28853479492a6fecc Mon Sep 17 00:00:00 2001
From: Joel Beckmeyer <joel@beckmeyer.us>
Date: Mon, 10 Jul 2023 10:17:05 -0400
Subject: [PATCH] coturn: update to 4.6.2.
---
srcpkgs/coturn/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/coturn/template b/srcpkgs/coturn/template
index bf23a22cf98f..28f848632fbe 100644
--- a/srcpkgs/coturn/template
+++ b/srcpkgs/coturn/template
@@ -1,7 +1,7 @@
# Template file for 'coturn'
pkgname=coturn
-version=4.6.0
-revision=4
+version=4.6.2
+revision=1
build_style=configure
configure_args="
--prefix=/usr
@@ -17,7 +17,7 @@ license="BSD-3-Clause"
homepage="https://github.com/coturn/coturn"
changelog="https://raw.githubusercontent.com/coturn/coturn/master/ChangeLog"
distfiles="https://github.com/coturn/coturn/archive/${version}.tar.gz"
-checksum=42206be7696014920dbe0ce309c602283ba71275eff51062e5456370fbacb863
+checksum=13f2a38b66cffb73d86b5ed24acba4e1371d738d758a6039e3a18f0c84c176ad
pre_build() {
# configure script does not like /usr when cross-building
next reply other threads:[~2023-07-10 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 14:22 TinfoilSubmarine [this message]
2023-07-10 20:52 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44961@inbox.vuxu.org \
--to=tinfoilsubmarine@users.noreply.github.com \
--cc=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).