From: iotku <iotku@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sublime-text4: update license_checksum
Date: Thu, 16 Jun 2022 20:21:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37586@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
There is a new pull request by iotku against master on the void-packages repository
https://github.com/iotku/void-packages master
https://github.com/void-linux/void-packages/pull/37586
sublime-text4: update license_checksum
#### Testing the changes
- I tested the changes in this PR: **YES**
Previously, the build would fail as the checksum of the license has changed.
I'm not aware of any notice of changes to the text, so it's likely just a minor formatting change in the html which is being check-summed. Additionally, sublime-merge-bin (sublime-text's sister project) uses the same EULA and respective checksum as provided here.
A patch file from https://github.com/void-linux/void-packages/pull/37586.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-37586.patch --]
[-- Type: text/x-diff, Size: 785 bytes --]
From 6521a632bccd81f27b83cd86130c39ff902ff436 Mon Sep 17 00:00:00 2001
From: Jonathan A <me@iotku.pw>
Date: Thu, 16 Jun 2022 11:06:42 -0700
Subject: [PATCH] sublime-text4: update license_checksum
---
srcpkgs/sublime-text4/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/sublime-text4/template b/srcpkgs/sublime-text4/template
index 8f3edc50ad74..e99798492daf 100644
--- a/srcpkgs/sublime-text4/template
+++ b/srcpkgs/sublime-text4/template
@@ -14,7 +14,7 @@ conflicts="sublime-text3"
repository="nonfree"
restricted=yes
nopie=yes
-_license_checksum=33929b71625d13dacf2a0a5853171b9c04058f71e2955ee660b8d0f8dda45ed1
+_license_checksum=287d037b0ecedb68ae1e3138411d54b87172156effecd1987a5f85834aa26a24
case "$XBPS_TARGET_MACHINE" in
x86_64)
next reply other threads:[~2022-06-16 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 18:21 iotku [this message]
2022-06-16 20:27 ` iotku
2022-06-16 20:35 ` [PR PATCH] [Closed]: " iotku
2022-06-16 20:43 [PR PATCH] " iotku
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-37586@inbox.vuxu.org \
--to=iotku@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).