From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] parsec: update to 150
Date: Mon, 06 Jan 2020 18:34:44 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18077@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
There is a new pull request by silvernode against master on the void-packages repository
https://github.com/silvernode/void-packages parsec
https://github.com/void-linux/void-packages/pull/18077
parsec: update to 150
A patch file from https://github.com/void-linux/void-packages/pull/18077.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-parsec-18077.patch --]
[-- Type: text/x-diff, Size: 1345 bytes --]
From 884cf247c875752c54e174f101608f72e8643231 Mon Sep 17 00:00:00 2001
From: mollusk <silvernode@gmail.com>
Date: Tue, 24 Dec 2019 00:55:58 -0700
Subject: [PATCH] parsec: update to 150
---
srcpkgs/parsec/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/parsec/template b/srcpkgs/parsec/template
index 403c1380b05..f20641a2611 100644
--- a/srcpkgs/parsec/template
+++ b/srcpkgs/parsec/template
@@ -1,6 +1,6 @@
# Template file for 'parsec'
pkgname=parsec
-version=147.9
+version=150
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=0741a0b535e676853a50d3ff1a6f6b2355fff127b6a0c0e503ad83818ef7bc74
nopie=yes
restricted=yes
@@ -21,6 +21,6 @@ do_extract() {
do_install() {
tar 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
+ mv ${DESTDIR}/usr/share/parsec/skel/parsecd-150-11.so ${DESTDIR}/usr/lib/parsec/parsecd-150-11.so
ln -rs ${DESTDIR}/usr/lib/parsec/parsecd-147-9.so ${DESTDIR}/usr/share/parsec/skel/
}
next reply other threads:[~2020-01-06 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 17:34 voidlinux-github [this message]
2020-01-08 17:29 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-08 17:33 ` voidlinux-github
2020-01-08 18:23 ` voidlinux-github
2020-01-08 21:34 ` voidlinux-github
2020-01-09 21:44 ` voidlinux-github
2020-01-12 3:27 ` voidlinux-github
2020-01-12 3:27 ` voidlinux-github
2020-01-12 6:51 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-12 9:56 ` voidlinux-github
2020-01-12 10:07 ` [PR PATCH] [Updated] parsec: update to 150 [ci-skip] voidlinux-github
2020-01-12 10:09 ` voidlinux-github
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-18077@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).