From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sublime-merge-bin: update to 2071.
Date: Sat, 30 Apr 2022 15:27:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36920@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
There is a new pull request by mobinmob against master on the void-packages repository
https://github.com/mobinmob/void-packages sublime-merge-bin
https://github.com/void-linux/void-packages/pull/36920
sublime-merge-bin: update to 2071.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/36920.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sublime-merge-bin-36920.patch --]
[-- Type: text/x-diff, Size: 1153 bytes --]
From 22852c40704789cf8135c565202fbea6ff8a9433 Mon Sep 17 00:00:00 2001
From: mobinmob <mobinmob@disroot.org>
Date: Sat, 30 Apr 2022 16:31:31 +0300
Subject: [PATCH] sublime-merge-bin: update to 2071.
---
srcpkgs/sublime-merge-bin/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/sublime-merge-bin/template b/srcpkgs/sublime-merge-bin/template
index 8c5cd2e290fe..73583df6b1ef 100644
--- a/srcpkgs/sublime-merge-bin/template
+++ b/srcpkgs/sublime-merge-bin/template
@@ -1,6 +1,6 @@
# Template file for 'sublime-merge-bin'
pkgname=sublime-merge-bin
-version=2068
+version=2071
revision=1
archs="x86_64"
wrksrc=sublime_merge
@@ -12,7 +12,7 @@ license="custom:EULA"
homepage="https://www.sublimemerge.com"
changelog="https://www.sublimemerge.com/download"
distfiles="https://download.sublimetext.com/sublime_merge_build_${version}_x64.tar.xz"
-checksum=0ac7994208eaafc07ae9295fff215966c9d115cdf3a8218a140cd274c45074d2
+checksum=c58564e45c7a55da07cdfd1c6e68702b212be470c46603e00e8056420fed4b45
_license_checksum=33929b71625d13dacf2a0a5853171b9c04058f71e2955ee660b8d0f8dda45ed1
nopie=yes
repository=nonfree
next reply other threads:[~2022-04-30 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 13:27 mobinmob [this message]
2022-06-10 19:54 ` [PR PATCH] [Closed]: " mobinmob
2022-05-03 8:37 [PR PATCH] " nonchip
2022-05-12 5:53 nonchip
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-36920@inbox.vuxu.org \
--to=mobinmob@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).