From: crtxcr <crtxcr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Signal-Desktop: update to 6.0.1.
Date: Tue, 06 Dec 2022 20:36:07 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40946@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
There is a new pull request by crtxcr against master on the void-packages repository
https://github.com/crtxcr/void-packages update_signal
https://github.com/void-linux/void-packages/pull/40946
Signal-Desktop: update to 6.0.1.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
CC @akierig
A patch file from https://github.com/void-linux/void-packages/pull/40946.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_signal-40946.patch --]
[-- Type: text/x-diff, Size: 1224 bytes --]
From 9fdd42f23ee833b5a5d74eb48fd7b4ffbb0ac827 Mon Sep 17 00:00:00 2001
From: Albert Schwarzkopf <dev-voidlinux@quitesimple.org>
Date: Tue, 6 Dec 2022 20:22:14 +0100
Subject: [PATCH] Signal-Desktop: update to 6.0.1.
---
srcpkgs/Signal-Desktop/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/Signal-Desktop/template b/srcpkgs/Signal-Desktop/template
index a87485f438be..6a1c46a883f4 100644
--- a/srcpkgs/Signal-Desktop/template
+++ b/srcpkgs/Signal-Desktop/template
@@ -1,6 +1,6 @@
# Template file for 'Signal-Desktop'
pkgname=Signal-Desktop
-version=6.0.0
+version=6.0.1
revision=1
# Signal officially only supports x86_64 (also due to Electron)
# x86_64-musl fails because of its dependency on 'node-gyp' which depends on a glibc specific extension
@@ -13,7 +13,7 @@ maintainer="akierig <anelki@fastmail.de>"
license="AGPL-3.0-only"
homepage="https://github.com/signalapp/Signal-Desktop"
distfiles="https://github.com/signalapp/Signal-Desktop/archive/v${version}.tar.gz"
-checksum=8ca77362a6f567c48cba798a4683499a8c651cefe67be2cdfc9c7fb4daf8800b
+checksum=b7c7b2824d1340ee4dee0a20ffe2883ccde610cb98b4f8d6d2b44f70130e384c
nostrip_files="signal-desktop"
post_extract() {
next reply other threads:[~2022-12-06 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 19:36 crtxcr [this message]
2022-12-07 0:18 ` [PR PATCH] [Merged]: " Piraty
2022-12-07 5:45 ` akierig
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-40946@inbox.vuxu.org \
--to=crtxcr@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).