From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Signal-Desktop: update to 6.20.0.
Date: Sat, 03 Jun 2023 20:23:41 +0200 [thread overview]
Message-ID: <20230603182341.sXzdVKShtK7ru0xJ77RF5fi_u81s1GZ-eXPB1uX3xVY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44205@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
There is an updated pull request by akierig against master on the void-packages repository
https://github.com/akierig/void-packages signal-6.20
https://github.com/void-linux/void-packages/pull/44205
Signal-Desktop: update to 6.20.0.
#### 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/44205.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-signal-6.20-44205.patch --]
[-- Type: text/x-diff, Size: 2025 bytes --]
From 2c8a73c3fd79bfe65ca2b601cf4c98254d152e80 Mon Sep 17 00:00:00 2001
From: anelki <akierig@fastmail.de>
Date: Wed, 31 May 2023 18:20:33 -0500
Subject: [PATCH] Signal-Desktop: update to 6.20.0.
---
srcpkgs/Signal-Desktop/template | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/Signal-Desktop/template b/srcpkgs/Signal-Desktop/template
index 4c6722055987..fec02583a29a 100644
--- a/srcpkgs/Signal-Desktop/template
+++ b/srcpkgs/Signal-Desktop/template
@@ -1,34 +1,38 @@
# Template file for 'Signal-Desktop'
pkgname=Signal-Desktop
-version=6.19.0
+version=6.20.0
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 nodejs python3 tar yarn"
+hostmakedepends="git git-lfs nodeenv 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=965702b217b39131c61e62c63fb25b073750a8f6febdffa9db236626124c6e50
+checksum=fc92011c51da6792215eb92d48afc17f1967caeade1307daaa13884244d7a3b0
nostrip_files="signal-desktop"
post_extract() {
# git-lfs hook needs to be installed for one of the dependencies
git lfs install
- #vsed 's/"node": "/&>=/' -i package.json
- vsed 's/"node": "18.14.0"/"node": ">=16.19.0"/' -i package.json
+ # use nodeenv since we have that in the repos already
+ nodeenv --node='18.14.0' signal-node
+ . ./signal-node/bin/activate
+
+ 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
}
next prev parent reply other threads:[~2023-06-03 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 23:22 [PR PATCH] " akierig
2023-05-31 23:49 ` [PR PATCH] [Updated] " akierig
2023-06-03 18:23 ` akierig [this message]
2023-06-03 18:50 ` [PR PATCH] [Merged]: " 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=20230603182341.sXzdVKShtK7ru0xJ77RF5fi_u81s1GZ-eXPB1uX3xVY@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).