Package Details: signal 1.27.4-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: 224
Popularity: 7.971038
First Submitted: 2016-08-17 22:58
Last Updated: 2019-10-10 20:24

Latest Comments

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

mbloms commented on 2019-09-26 13:31

@dbirks oh, that makes sense. (what I meant about git being less secure is that I can't know whether the commit has changed since the tag was made, but yeah of course it's more secure than an unhashed tar ball source)

dbirks commented on 2019-09-26 13:10

Jake: Thank you for catching that and reverting.

Jake commented on 2019-09-26 09:34

dbirks: No, it was not not because of GPG, the reason was this: https://github.com/signalapp/Signal-Desktop/issues/2376 And as gj545rndmu wrote this is still happening. I have reverted the commit now. The bug is not obvious, because it picks up the git info from the AUR repo and the packages are usually build inside that repo (especially as maintainer). Otherwise we would have to patch the build process. Since git does some internal hash checking and the transfer is TLSv1.3 encrypted i don't see an security issue with git.

gj545rndmu commented on 2019-09-26 06:58

Cannot update to current version 1.27.3-1. I get following error!?

Running "getExpireTime" task
Warning: Cannot read property 'branch' of undefined Use --force to continue.

Aborted due to warnings.
error Command failed with exit code 3.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 3.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...

dbirks commented on 2019-09-26 02:07

mbloms: looks like using git for source was from when we were trying to do a gpg check on the git tag. That ended up not working out, but it looks like I didn't switch back. Just now did. Thanks for asking about it!

mbloms commented on 2019-09-25 22:18

Is there a reason to use git rather than just using the release tar-ball as source? git is slower and since it can't be hashed, less secure.

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.