Github messages for voidlinux
 help / color / mirror / Atom feed
From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Signal-Desktop: update to 6.12.0, add aarch64
Date: Thu, 30 Mar 2023 00:36:31 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43107@inbox.vuxu.org> (raw)

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

There is a new pull request by akierig against master on the void-packages repository

https://github.com/akierig/void-packages signal-6.12
https://github.com/void-linux/void-packages/pull/43107

Signal-Desktop: update to 6.12.0, add aarch64
#### 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/43107.patch is attached

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

From e2b8389e3b7ce73eeb1428fad52be80e8f9a8eca Mon Sep 17 00:00:00 2001
From: anelki <akierig@fastmail.de>
Date: Wed, 29 Mar 2023 17:35:27 -0500
Subject: [PATCH] Signal-Desktop: update to 6.12.0.

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

diff --git a/srcpkgs/Signal-Desktop/template b/srcpkgs/Signal-Desktop/template
index 914c8d428531..4f9f19295dcf 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.11.0
+version=6.12.0
 revision=1
 # Signal officially only supports x86_64 
 # x86_64-musl fails because of its dependency on 'node-gyp' which depends on a glibc specific extension
@@ -9,11 +9,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="akierig <anelki@fastmail.de>"
+maintainer="anelki <akierig@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=1dfc7ce32b663c37513303fe102fd154ae767b5b425885b9e56fc1e46c2af2fd
+checksum=c07dccc9c032623e3b93eda2992da1c59e2dc6a93c84646d0d5bbfe4e08de4d6
 nostrip_files="signal-desktop"
 
 post_extract() {
@@ -28,7 +28,7 @@ post_extract() {
 
 do_build() {
 	yarn generate
-	yarn build-release
+	bash -c 'yarn build-release'
 }
 
 do_install() {

             reply	other threads:[~2023-03-29 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 22:36 akierig [this message]
2023-03-29 22:37 ` [PR REVIEW] " classabbyamp
2023-03-29 22:39 ` akierig
2023-03-29 22:42 ` [PR PATCH] [Updated] " akierig
2023-03-29 23:03 ` akierig
2023-03-29 23:12 ` akierig
2023-03-29 23:28 ` [PR PATCH] [Merged]: Signal-Desktop: update to 6.12.0 abenson

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-43107@inbox.vuxu.org \
    --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).