Package Details: signal-desktop-bin 1.14.3-1

Git Clone URL: https://aur.archlinux.org/signal-desktop-bin.git (read-only)
Package Base: signal-desktop-bin
Description: Private messaging from your desktop
Upstream URL: https://github.com/signalapp/Signal-Desktop
Keywords: messenger secure
Licenses: GPL3
Conflicts: signal
Provides: signal-desktop
Submitter: jbbr
Maintainer: jbbr
Last Packager: jbbr
Votes: 76
Popularity: 11.666048
First Submitted: 2017-10-31 20:04
Last Updated: 2018-07-19 19:39

Latest Comments

r4mp commented on 2018-05-15 08:00

@jbbr: jfyi today version 1.11.0 was released

The new sha512 sum should be: 776f3e75ef304af5da72cc6e67b3cf541183bc461cffa38e575a4f9019a088553983c2ed7b5381de85f68f2228cc3505384337e6cf621019ef0cd3f83b60aeac

jbbr commented on 2018-05-11 22:36

@LA-MJ: Thanks, this was due to a new patch release 1.10.1. I updated the package, it should work now

LA-MJ commented on 2018-05-11 21:18

404

Oliver87 commented on 2018-05-02 05:52

@jbbr: Thanks for fixing and providing!

@christianbundy: I installed it your suggested way and it worked fine omitting the brackets encasing the URL. Learnt another thing today, thank you!

jbbr commented on 2018-05-02 02:26

@awc: Thanks for the report. This is caused by changes of directory permissions in the upstream .deb-package. I published a new release of this PKGBUILD which changes directory permissions in the package to 755. The issues should be gone once you upgrade the package without interfering manually.

awc commented on 2018-05-02 01:44

With the update to 1.9.0-1, I'm getting warnings that the directory permissions differ in /opt/Signal/. The filesystem is 755 and the package is 775. Is this something I should interfere with manually?

jbbr commented on 2018-05-01 17:27

Thanks for reporting this, I fixed the hash and compared it to the hash in https://updates.signal.org/desktop/apt/dists/xenial/main/binary-amd64/Packages It should work now.

Sorry about that, I don't know whether I added the wrong hash or OWS update the deb-file. It's a bit odd that this only gets reported now, 6 days after the release. Does anyone have the old .deb-file and could compare it's contents? I assume the official repo can be trusted, I'm just curious.

vbmithr commented on 2018-05-01 17:13

Same here. Not passing SHA512 sum.

christianbundy commented on 2018-05-01 16:34

Oliver86: can you try without pamac?

  • git clone <https://aur.archlinux.org/signal-desktop-bin.git>
  • cd signal-desktop-bin
  • makepkg -si

Oliver87 commented on 2018-05-01 16:26

The file signal-desktop_1.8.0_amd64.deb didn't pass the sha512sums check. I do not know how to solve this. (I was using pamac)

@jbbr Thanks for your effort!

jbbr commented on 2018-04-01 04:44

@DescartesHorse I updated the URL, thanks

DescartesHorse commented on 2018-04-01 03:16

I realise it's more semantics, given it's not actually used in your PKGBUILD, but you may want to adjust URL to reflect that the repo's have moved to https://github.com/signalapp :)

gabriwinter commented on 2018-02-01 16:50

1.3 Is out.

Just tested your PKGBUILD with it and it installs fine. Can you please update it?

privong commented on 2017-11-01 02:58

@jbbr great, thanks, will try again soon. Yep, thanks for the clarification about the package difference. I realized that when I tried building the one from source and realized it was different from the other (pre-compiled) electron apps I'd been installing through AUR.

jbbr commented on 2017-11-01 01:53

Thanks for reporting @privong. This should be fixed now.

Btw: The difference between this package and "signal" is that this is using the prebuilt binaries from the official Ubuntu Apt repository. The "signal" package builds from source.

privong commented on 2017-11-01 01:46

The compiled package does not work because the symbolic link created in /usr/bin points to the /tmp directory in which the package was created. That directory is cleared, so the binary no longer exists.

$ ls -l /usr/bin/signal-desktop
lrwxrwxrwx 1 root root 60 Oct 31 21:42 /usr/bin/signal-desktop -> /tmp/yaourt-tmp-username/aur-signal-desktop-bin/signal-desktop

I think this is a problem with the {pkgdir} variable, but I am not sure...