From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: discord-ptb: update to 0.0.35.
Date: Wed, 09 Nov 2022 15:54:39 +0100 [thread overview]
Message-ID: <20221109145439.GljBchc1USjhKAfhWfdzW-ck_OMCbQPKGUtjs2_cmHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40401@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/40401#issuecomment-1308885276
Comment:
> The EULA hash has been giving me trouble for weeks.
They just keep changing formatting, this time it was a single space:
```diff
--- /usr/share/licenses/discord-ptb/EULA 2022-10-20 14:45:47.000000000 -0400
+++ masterdir/destdir/discord-ptb-0.0.34/usr/share/licenses/discord-ptb/EULA 2022-11-09 08:28:35.000000000 -0500
@@ -76,7 +76,7 @@ Together, these rules make Discord possi
believe others aren<E2><80><99>t following them, please let us know: https://dis.gd/report
.
-<E2><80><8D>IMPORTANT NOTE:The section titled <E2><80><9C>Settling Disputes Between You and Discord<E2><80><9D>
+<E2><80><8D>IMPORTANT NOTE: The section titled <E2><80><9C>Settling Disputes Between You and Discord<E2><80><9D>
contains an arbitration clause and class-action waiver that applies to all
U.S.-based Discord users. Please read this section carefully as it may
significantly affect your legal rights, including your right to file a lawsuit
```
At this point it's starting look like convincing them to add the EULA in the distfile would be easier than playing wack-a-mole with formatting changes that happen in-between template updates.
next prev parent reply other threads:[~2022-11-09 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 1:34 [PR PATCH] " Seltyk
2022-11-09 14:54 ` 0x5c [this message]
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=20221109145439.GljBchc1USjhKAfhWfdzW-ck_OMCbQPKGUtjs2_cmHc@z \
--to=0x5c@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).