Github messages for voidlinux
 help / color / mirror / Atom feed
From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Signal-Desktop: update to 5.43.0, adopt.
Date: Fri, 13 May 2022 02:26:14 +0200	[thread overview]
Message-ID: <20220513002614.3TACfZmdhqU_bB6IHi6y5Bqd8I3e2kbCyx1BCATd5Oo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36992@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 494 bytes --]

There is an updated pull request by akierig against master on the void-packages repository

https://github.com/akierig/void-packages signal-5.42
https://github.com/void-linux/void-packages/pull/36992

Signal-Desktop: update to 5.43.0, adopt.
#### 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**

A patch file from https://github.com/void-linux/void-packages/pull/36992.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-signal-5.42-36992.patch --]
[-- Type: text/x-diff, Size: 1406 bytes --]

From 6ba2f9d6ad34cbea50405db8f2509b61a50d3904 Mon Sep 17 00:00:00 2001
From: akierig <anelki@fastmail.de>
Date: Thu, 5 May 2022 15:18:37 -0500
Subject: [PATCH] Signal-Desktop: update to 5.43.0, adopt

---
 srcpkgs/Signal-Desktop/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/Signal-Desktop/template b/srcpkgs/Signal-Desktop/template
index 43e11503bd50..aee39932147e 100644
--- a/srcpkgs/Signal-Desktop/template
+++ b/srcpkgs/Signal-Desktop/template
@@ -1,6 +1,6 @@
 # Template file for 'Signal-Desktop'
 pkgname=Signal-Desktop
-version=5.41.0
+version=5.43.0
 revision=1
 # Signal officially only supports x86_64 (also due to Electron)
 # discontinued Electron 32-bit support: https://www.electronjs.org/blog/linux-32bit-support
@@ -10,11 +10,11 @@ archs="x86_64"
 hostmakedepends="git git-lfs nodejs python3 tar yarn"
 depends="cairo gtk+3 libvips pango"
 short_desc="Signal Private Messenger for Linux"
-maintainer="Orphaned <orphan@voidlinux.org>"
+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=55a201912f5a41c1a76d210d3942078e734ac619df7ffb56083149ce4995e949
+checksum=9239dfc0356cec3c0aaea93e09d0ac44030037f24c1dcc3725e1e417c74af419
 nostrip_files="signal-desktop"
 
 post_extract() {

  parent reply	other threads:[~2022-05-13  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 20:20 [PR PATCH] Signal-Desktop: update to 5.42.0 akierig
2022-05-06  9:34 ` paper42
2022-05-09  1:56 ` akierig
2022-05-13  0:22 ` [PR PATCH] [Updated] " akierig
2022-05-13  0:24 ` [PR PATCH] [Updated] Signal-Desktop: update to 5.43.0, adopt akierig
2022-05-13  0:25 ` akierig
2022-05-13  0:26 ` akierig [this message]
2022-05-13  8:48 ` [PR PATCH] [Merged]: " paper42

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=20220513002614.3TACfZmdhqU_bB6IHi6y5Bqd8I3e2kbCyx1BCATd5Oo@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).