From: Seltyk <Seltyk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] discord-ptb: update to 0.0.35.
Date: Wed, 09 Nov 2022 02:34:31 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40401@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
There is a new pull request by Seltyk against master on the void-packages repository
https://github.com/Seltyk/void-packages dptb-update
https://github.com/void-linux/void-packages/pull/40401
discord-ptb: update to 0.0.35.
#### Testing the changes
- I tested the changes in this PR: **briefly**
---
The EULA hash has been giving me trouble for weeks. Perhaps this is only an issue on my machine? The CI will confirm. Also, there is no need to `cat ` into `w3m`, it can read files directly.
A patch file from https://github.com/void-linux/void-packages/pull/40401.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-dptb-update-40401.patch --]
[-- Type: text/x-diff, Size: 1525 bytes --]
From 97cc0109abcd5c304c77b77eb0d09b1f1291da6e Mon Sep 17 00:00:00 2001
From: Seltyk <whhacker.dcx@gmail.com>
Date: Tue, 8 Nov 2022 20:33:02 -0500
Subject: [PATCH] discord-ptb: update to 0.0.35.
---
srcpkgs/discord-ptb/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/discord-ptb/template b/srcpkgs/discord-ptb/template
index b74f2078278f..c62aa25f774d 100644
--- a/srcpkgs/discord-ptb/template
+++ b/srcpkgs/discord-ptb/template
@@ -1,6 +1,6 @@
# Template file for 'discord-ptb'
pkgname=discord-ptb
-version=0.0.34
+version=0.0.35
revision=1
archs="x86_64"
hostmakedepends="w3m"
@@ -11,15 +11,15 @@ maintainer="0x5c <dev@0x5c.io>"
license="custom:Proprietary"
homepage="https://discord.com/"
distfiles="https://dl-ptb.discordapp.net/apps/linux/${version}/discord-ptb-${version}.tar.gz"
-checksum=083e9d2e806796f869c0415f2c8f4eaa386f8993e3df1343c8f2bda81254a9c9
-_license_checksum=b64b3fdcd86d70df0e4dffa8d4aa4a7aa3e87204059902f1680100f5ee2f2ef4
+checksum=6e7a79c1f711db5b3b2cc3f11608f91b752cc4f5a5163e2de826dea2c8ae7c76
+_license_checksum=45e63af835972e94b311bc44d515ca11a919d6a8f127ec801267b0a8fba10847
nopie=yes
restricted=yes
repository=nonfree
post_extract() {
- $XBPS_FETCH_CMD -o eula https://discord.com/terms; cat eula |
- w3m -dump -I utf-8 -T text/html |
+ $XBPS_FETCH_CMD -o eula https://discord.com/terms
+ w3m -dump -I utf-8 -T text/html eula |
sed -n '/Discord.s Terms of Service/,/^Imagine a place$/p' > EULA
filesum="$(xbps-digest EULA)"
next reply other threads:[~2022-11-09 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 1:34 Seltyk [this message]
2022-11-09 14:54 ` 0x5c
2022-11-10 22:01 ` [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-40401@inbox.vuxu.org \
--to=seltyk@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).