Package Details: signal 1.7.1-1

Git Clone URL: https://aur.archlinux.org/signal.git (read-only)
Package Base: signal
Description: Signal Private Messenger for the Desktop
Upstream URL: https://github.com/signalapp/Signal-Desktop
Keywords: messenger secure
Licenses: GPL3
Conflicts: signal-desktop, signal-desktop-beta, signal-desktop-bin
Provides: signal
Submitter: onny
Maintainer: dbirks (Jake)
Last Packager: Jake
Votes: 118
Popularity: 20.293013
First Submitted: 2016-08-17 22:58
Last Updated: 2018-04-14 09:21

Latest Comments

Powersource commented on 2018-04-14 11:01

Build is failing for me, getting the same error after running the suggested command:

Run npm config delete prefix or nvm use --delete-prefix v8.2.1 to unset it. Found '/mnt/hdd/home/me/.cache/pacaur/signal/src/signal-git-repo/.nvmrc' with version <8.2.1> nvm is not compatible with the npm config "prefix" option: currently set to "/mnt/hdd/home/me/.nvm/versions/node/v8.2.1

Jake commented on 2018-04-14 09:24

We used the tarball in the past, but that caused build problems. Please take a look at the AUR history and older comments from hero.

Never thought about that, but i understand that it could be annoying for people on slow connections. Talking about disk space the additional 50 MB for the repo are quite insignificant though, after it created more than 1 GB in node modules... Reusing the repo is nonetheless a good idea and seems to work perfectly fine, so i have changed the location now.

jonathon commented on 2018-04-13 23:43

Please consider downloading the source tarball instead of the entire git repo for every pkgver, i.e.:

source=("${pkgname}-${pkgver}.tar.gz::https://github.com/signalapp/Signal-Desktop/archive/v${pkgver}.tar.gz"

instead of

source=("${pkgname}-${pkgver}::git+https://github.com/signalapp/Signal-Desktop.git#tag=v${pkgver}"

It will save an awful lot of time, disk space, and data transfer.

Alternatively, if you are going to clone the git repo at least clone it to the same location so it can be reused for later pkgver, e.g.:

source=("${pkgname}::git+https://github.com/signalapp/Signal-Desktop.git#tag=v${pkgver}"

weirddan455 commented on 2018-03-31 02:33

Nevermind, I got it installed. I think it was just having trouble downloading a file.

weirddan455 commented on 2018-03-31 01:31

I'm getting an error trying to build this package. Looked through previous comments and didn't see anything related. Anyone have any suggestions?

https://pastebin.com/ZQ80P2UB

jplatte commented on 2018-03-17 14:54

@Jake: Sorry, I didn't read the error message carefully enough. I have NPM_PACKAGES="$HOME/.npm-packages" in my .zshrc because I sometimes want to install stuff for my user but never for the whole system with npm -g (not without going through pacman). I haven't seen this environment variable causing issues when building other packages that use npm.

Jake commented on 2018-03-15 16:51

@benwaffle: I have added a workaround for the prefix config, please try it again now.

@jplatte: That is odd, if you didn't set the prefix somehow in the meantime? Even if the build aborted i can't think of how the prefix gets to ~/.npm-packages... Does it build now?

buzo commented on 2018-03-15 09:38

FWIW, this update made me switch to the AUR package signal-desktop-bin, because this electron/yarn/nvm stuff is an increasing PITA to handle.

jplatte commented on 2018-03-15 07:31

For me, only the first build with nvm worked (before nvm, I never had the problems others reported). I haven't configured nvm in any way, it was only installed when it was first added as a build dep for signal, but now I'm getting the following error:

v8.2.1 is already installed. nvm is not compatible with the npm config "prefix" option: currently set to "/home/jplatte/.npm-packages" Run npm config delete prefix or nvm use --delete-prefix v8.2.1 to unset it. Found '/home/jplatte/.cache/pacaur/signal/src/signal-1.6.0/.nvmrc' with version <8.2.1> v8.2.1 is already installed. nvm is not compatible with the npm config "prefix" option: currently set to "/home/jplatte/.npm-packages" Run npm config delete prefix or nvm use --delete-prefix v8.2.1 to unset it. Found '/home/jplatte/.cache/pacaur/signal/src/signal-1.6.0/.nvmrc' with version <8.2.1> nvm is not compatible with the npm config "prefix" option: currently set to "/home/jplatte/.npm-packages" Run npm config delete prefix or nvm use --delete-prefix v8.2.1 to unset it.

benwaffle commented on 2018-03-15 04:02

@Jake - I don't want to use nvm for my system, I'd rather just have the latest nodejs package from the arch repos. I'm not suggesting dropping nvm, I am just wondering if there is a way that we can support building Signal even with a custom prefix

All comments