Github messages for voidlinux
 help / color / mirror / Atom feed
From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] teamspeak3: update to 3.5.2.
Date: Fri, 17 Apr 2020 19:01:58 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21081@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

There is a new pull request by HadetTheUndying against master on the void-packages repository

https://github.com/HadetTheUndying/void-packages teamspeak3
https://github.com/void-linux/void-packages/pull/21081

teamspeak3: update to 3.5.2.
32-bit might be failing to build. Had it happen once then build the second time(No idea why), but since this isn't a repo package i decided to push anyway.

A patch file from https://github.com/void-linux/void-packages/pull/21081.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-teamspeak3-21081.patch --]
[-- Type: text/x-diff, Size: 1408 bytes --]

From e5ad293e9e2d765746e143fb7188c12d4bc7c542 Mon Sep 17 00:00:00 2001
From: HadetTheUndying <hadet@protonmail.com>
Date: Fri, 17 Apr 2020 11:57:00 -0500
Subject: [PATCH] teamspeak3: update to 3.5.2.

---
 srcpkgs/teamspeak3/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/teamspeak3/template b/srcpkgs/teamspeak3/template
index a31343fe68a..9e959cd1d53 100644
--- a/srcpkgs/teamspeak3/template
+++ b/srcpkgs/teamspeak3/template
@@ -1,6 +1,6 @@
 # Template file for 'teamspeak3'
 pkgname=teamspeak3
-version=3.5.0
+version=3.5.2
 revision=1
 archs="i686 x86_64"
 wrksrc=teamspeak3
@@ -21,11 +21,11 @@ noverifyrdeps=yes
 if [ "$XBPS_TARGET_MACHINE" = "x86_64" ]; then
 	_pkg="TeamSpeak3-Client-linux_amd64-${version}"
 	distfiles="https://files.teamspeak-services.com/releases/client/${version}/${_pkg}.run"
-	checksum=17d53f116f38519d41749d5b07059e1791a533d0bcee052052b0b6b41f015912
+	checksum=d739fa78b41ef7b1423771ca237804981ffc7f14c4e620769cfa3fbc538aece8
 elif [ "$XBPS_TARGET_MACHINE" = "i686" ]; then
 	_pkg="TeamSpeak3-Client-linux_x86-${version}"
 	distfiles="https://files.teamspeak-services.com/releases/client/${version}/${_pkg}.run"
-	checksum=6ed3a4255c4785437668748b5a8f39895678cd57133150c33302a94421c5ffeb
+	checksum=209375141ea0d0fc1d6dc7612cb621ba0df946e033a3b1140f3e8a5c8938d566
 else
 	broken="No known upstream client for this architecture"
 fi

             reply	other threads:[~2020-04-17 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 17:01 HadetTheUndying [this message]
2020-04-17 18:54 ` Piraty
2020-04-17 18:59 ` [PR PATCH] [Updated] " HadetTheUndying
2020-04-17 19:00 ` HadetTheUndying
2020-04-17 21:24 ` Johnnynator
2020-04-17 21:40 ` HadetTheUndying
2020-04-17 21:43 ` Johnnynator
2020-04-17 21:44 ` [PR PATCH] [Updated] " HadetTheUndying
2020-04-17 21:46 ` HadetTheUndying
2020-04-17 22:21 ` [PR PATCH] [Merged]: " Johnnynator

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-21081@inbox.vuxu.org \
    --to=hadettheundying@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).