From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Signal-Desktop: update to 6.1.0.
Date: Sun, 18 Dec 2022 19:46:10 +0100 [thread overview]
Message-ID: <20221218184610.hwpVIOY1okxHdga_bkIWQwy5Ie8524YlLmK4hSIjNuk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41120@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
There is an updated pull request by akierig against master on the void-packages repository
https://github.com/akierig/void-packages signal-6.1
https://github.com/void-linux/void-packages/pull/41120
Signal-Desktop: update to 6.1.0.
#### Testing the changes
- I tested the changes in this PR: **NO**
A patch file from https://github.com/void-linux/void-packages/pull/41120.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-signal-6.1-41120.patch --]
[-- Type: text/x-diff, Size: 1203 bytes --]
From 7fab7a2d9c3c7b6aa16c22d330da1d1b17b0eef7 Mon Sep 17 00:00:00 2001
From: akierig <anelki@fastmail.de>
Date: Sun, 18 Dec 2022 12:04:31 -0600
Subject: [PATCH] Signal-Desktop: update to 6.1.0.
---
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 6a1c46a883f4..19a326e55f17 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.1
+version=6.1.0
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=b7c7b2824d1340ee4dee0a20ffe2883ccde610cb98b4f8d6d2b44f70130e384c
+checksum=f981ca229651826dcf2b511499612217719827ab98edac46f931fe2751eccd6f
nostrip_files="signal-desktop"
post_extract() {
next prev parent reply other threads:[~2022-12-18 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 19:30 [PR PATCH] [WIP] " akierig
2022-12-15 19:31 ` akierig
2022-12-18 12:04 ` paper42
2022-12-18 17:53 ` [PR PATCH] [Updated] " akierig
2022-12-18 17:56 ` akierig
2022-12-18 18:05 ` akierig
2022-12-18 18:46 ` akierig [this message]
2022-12-18 18:48 ` akierig
2022-12-18 22:18 ` [PR PATCH] [Merged]: " paper42
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 17:40 [PR PATCH] " akierig
2022-12-15 17:40 ` [PR PATCH] [Updated] " 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=20221218184610.hwpVIOY1okxHdga_bkIWQwy5Ie8524YlLmK4hSIjNuk@z \
--to=akierig@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).