From: Nicop06 <Nicop06@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] parsec: upgrade to 150.28
Date: Sat, 09 May 2020 21:59:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21800@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
There is a new pull request by Nicop06 against master on the void-packages repository
https://github.com/Nicop06/void-packages parsec
https://github.com/void-linux/void-packages/pull/21800
parsec: upgrade to 150.28
None
A patch file from https://github.com/void-linux/void-packages/pull/21800.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-parsec-21800.patch --]
[-- Type: text/x-diff, Size: 1455 bytes --]
From aab1b35f56f583050f30154f211f1e3418d18fb7 Mon Sep 17 00:00:00 2001
From: Nicolas Porcel <nicolasporcel06@gmail.com>
Date: Sat, 9 May 2020 15:31:16 +0100
Subject: [PATCH] parsec: upgrade to 150.28
---
srcpkgs/parsec/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/parsec/template b/srcpkgs/parsec/template
index 6a2baa168c8..ba9141c2118 100644
--- a/srcpkgs/parsec/template
+++ b/srcpkgs/parsec/template
@@ -1,6 +1,6 @@
# Template file for 'parsec'
pkgname=parsec
-version=147.9
+version=150.28
revision=1
archs="x86_64"
build_style=fetch
@@ -10,7 +10,7 @@ maintainer="Kozova1 <mug66kk@gmail.com>"
license="Proprietary"
homepage="https://parsecgaming.com"
distfiles="https://s3.amazonaws.com/parsec-build/package/parsec-linux.deb"
-checksum=beed951ebee0189e8c22aa3d9190e1ddc7691c4703379e146a8b812c21b3a273
+checksum=0c7207f419377fc35e30448acd00d8701300ac5a44936ac6d87a468c9afccdc1
nopie=yes
restricted=yes
@@ -21,6 +21,6 @@ do_extract() {
do_install() {
bsdtar xf "data.tar.xz" -C ${DESTDIR}
vmkdir usr/lib/parsec
- mv ${DESTDIR}/usr/share/parsec/skel/parsecd-147-9.so ${DESTDIR}/usr/lib/parsec/parsecd-147-9.so
- ln -rs ${DESTDIR}/usr/lib/parsec/parsecd-147-9.so ${DESTDIR}/usr/share/parsec/skel/
+ mv ${DESTDIR}/usr/share/parsec/skel/parsecd-150-28.so ${DESTDIR}/usr/lib/parsec/parsecd-150-28.so
+ ln -rs ${DESTDIR}/usr/lib/parsec/parsecd-150-28.so ${DESTDIR}/usr/share/parsec/skel/
}
next reply other threads:[~2020-05-09 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 19:59 Nicop06 [this message]
2020-05-10 12:03 ` [PR PATCH] [Merged]: " Hoshpak
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-21800@inbox.vuxu.org \
--to=nicop06@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).