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.20.1.
Date: Wed, 07 Jun 2023 06:04:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44302@inbox.vuxu.org> (raw)

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

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

https://github.com/akierig/void-packages signal-6.20.1
https://github.com/void-linux/void-packages/pull/44302

Signal-Desktop: update to 6.20.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


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

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

From 2d799c8f93ebae39894b1a68466a296cc079c038 Mon Sep 17 00:00:00 2001
From: anelki <akierig@fastmail.de>
Date: Tue, 6 Jun 2023 20:24:30 -0500
Subject: [PATCH] Signal-Desktop: update to 6.20.1.

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

diff --git a/srcpkgs/Signal-Desktop/template b/srcpkgs/Signal-Desktop/template
index fec02583a29a..7eca75b4f1f5 100644
--- a/srcpkgs/Signal-Desktop/template
+++ b/srcpkgs/Signal-Desktop/template
@@ -1,38 +1,34 @@
 # Template file for 'Signal-Desktop'
 pkgname=Signal-Desktop
-version=6.20.0
+version=6.20.1
 revision=1
 # Signal officially only supports x86_64 
 # x86_64-musl could potentially work based on the Alpine port:
 # https://git.alpinelinux.org/aports/tree/testing/signal-desktop
 # ARM: https://github.com/signalapp/Signal-Desktop/issues/3410
 archs="x86_64"
-hostmakedepends="git git-lfs nodeenv python3 tar"
+hostmakedepends="git git-lfs nodejs python3 tar"
 depends="cairo gtk+3 libvips pango"
 short_desc="Signal Private Messenger for Linux"
 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=fc92011c51da6792215eb92d48afc17f1967caeade1307daaa13884244d7a3b0
+checksum=3c664dbb5c1670554859fa55fd765ac35632f573fd5b7bea63876cdf41b6b7d6
 nostrip_files="signal-desktop"
 
 post_extract() {
 	# git-lfs hook needs to be installed for one of the dependencies
 	git lfs install
 
-	# use nodeenv since we have that in the repos already
-	nodeenv --node='18.14.0' signal-node
-	. ./signal-node/bin/activate
+	vsed 's/"node": "/&>=/' -i package.json
 
 	npm install -g yarn
-
 	# Dependencies have to be installed before applying patch
 	yarn install --ignore-engines --frozen-lockfile
 }
 
 do_build() {
-	. ./signal-node/bin/activate
 	yarn generate
 	yarn build-release
 }

             reply	other threads:[~2023-06-07  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  4:04 akierig [this message]
2023-06-07 13:11 ` [PR REVIEW] " paper42
2023-06-07 14:33 ` akierig
2023-06-08 22:47 ` [PR PATCH] [Merged]: " classabbyamp

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-44302@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).