Package Details: signal 1.27.2-1

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

kaefert commented on 2019-09-12 11:42

@baur thanks for your hint's about problem beeing linked with locale settings. After I fixed this problem (with a reboot) I could successfully upgrade signal :)

baur commented on 2019-09-12 09:35

kaefert: I had a very similar error message from $ makepkg -si preceded by an error related to my locale settings

/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_DE.UTF-8)
gyp: Call to 'node -e "require('nan')"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/node-gyp/lib/configure.js:323:16)
gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 4.19.69-1-MANJARO
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/username/builds/signal/src/signal-git-repo/node_modules/spellchecker
gyp ERR! node -v v12.9.1
gyp ERR! node-gyp -v v5.0.2
gyp ERR! not ok

What did the trick for me was exchanging the nonexistent locale en_DE by something actually existing like en_GB or de_DE (https://wiki.manjaro.org/index.php?title=Locale).

PS: This is my very first contribution on archlinux.org. In case I did something wrong please advice me on where to find guidelines or conventions I missed.

kaefert commented on 2019-09-06 17:20

dbirks: thanks for that hint, got me a bit further:

gyp: Call to 'node -e "require('nan')"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/username/.nvm/versions/node/v12.10.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)
gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 4.19.66-1
gyp ERR! command "/home/username/.nvm/versions/node/v12.10.0/bin/node" "/home/username/.nvm/versions/node/v12.10.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/username/.cache/pacaur/signal/src/signal-git-repo/node_modules/spellchecker
gyp ERR! node -v v12.10.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok

dbirks commented on 2019-09-06 17:04

kaefert: The only thing I can think of is to double check that your repos are up to date. Haven't used pacaur for a while, but looks like pacaur -Sya would do it.

kaefert commented on 2019-09-06 16:55

doesn't work for me:

$ pacaur -Sa signal
:: resolving dependencies...
:: no results found for nodejs>=12 (dependency tree: signal nodejs)

j0hannes commented on 2019-09-06 13:18

(edit) now it ran through without any problem

dbirks commented on 2019-09-06 12:57

SpotlightKid: nodejs-lts-dubnium used to be the dependency I had before Signal updated its node version. I've set the dependency here to nodejs>=12 now, hopefully to enforce the community/nodejs package.

SpotlightKid commented on 2019-09-06 12:30

I had the same error as j0hannes. Turned out that I had community/nodejs-lts-dubnium installed instead of community/nodejs. I have no idea, how that came to be. However I installed community/nodejs instead and that fixed it.

j0hannes commented on 2019-09-06 11:48

@simon1573, maybe your setup fulfills the dependency already. I don't use nodejs, that's why the package is not installed. It is listed as a dependency in the PKGBUILD, but without specifying a version, though.

Kandelborg commented on 2019-09-06 11:34

I also experienced the node version error. I fixed it by installing nvm from the AUR and installing node v12.10.

yay -Sy nvm
source /usr/share/nvm/init-nvm.sh >> ~/.zshrc # Or bashrc or some other
nvm ls-remote # list available versions
nvm install 12.10
npm config delete prefix # I got a warning telling me to do this, you might not have to.
nvm use 12
yay -Syu

Then i could successfully upgrade signal.