Package Details: signal-cli 0.10.2-1

Git Clone URL: https://aur.archlinux.org/signal-cli.git (read-only, click to copy)
Package Base: signal-cli
Description: Provides a commandline and dbus interface for secure Signal messaging.
Upstream URL: https://github.com/AsamK/signal-cli
Keywords: cli dbus json-rpc messaging signal
Licenses: GPL3
Submitter: AsamK
Maintainer: AsamK
Last Packager: AsamK
Votes: 27
Popularity: 0.116519
First Submitted: 2016-04-02 11:44
Last Updated: 2022-01-22 22:12

Dependencies (7)

Required by (2)

Sources (3)

Pinned Comments

stas-t commented on 2021-12-12 13:54

Java 17 is now both build and runtime requirement, however having it installed is not enough: it needs to be either set as a default:

archlinux-java set java-17-openjdk

or the scripts should use Java 17 specifically.

AsamK commented on 2017-06-17 12:24

I've added a pgp signature to the source file, to import the signing key, run the following command:

gpg --keyserver hkps://keys.openpgp.org --recv-keys FA10826A74907F9EC6BBB7FC2BA2CD21B5B09570

Latest Comments

1 2 3 Next › Last »

atcw commented on 2022-01-29 01:36

just to be more verbose (and for SEO purposes):

FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':lib:compileJava'.
> error: invalid source release: 17

is solved by

archlinux-java set java-17-openjdk

stas-t commented on 2021-12-12 13:54

Java 17 is now both build and runtime requirement, however having it installed is not enough: it needs to be either set as a default:

archlinux-java set java-17-openjdk

or the scripts should use Java 17 specifically.

magamo commented on 2021-09-07 13:32

Hi, I'm also getting the error that the signing key cannot be imported (gpg: keyserver receive failed: No name), and have tried all manual commands in the comments to get past this. Any further advice? Thanks!

the_10 commented on 2021-07-01 07:37

The gpg key import failed with

gpg --recv-keys FA10826A74907F9EC6BBB7FC2BA2CD21B5B09570
gpg: keyserver receive failed: No keyserver available

PhotonX commented on 2021-02-14 18:43

I now realised, the pinned comment solves my issue. :D However, I have a new issue now. After many successful compilations I get the following error: https://pastebin.com/DDntZvRn

PhotonX commented on 2021-01-28 14:10

Same problem as rixx here.

rixx commented on 2020-12-06 20:24

==> Starting build()...
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.7/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing
> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not target platform: 'Java SE 11' using tool chain: 'JDK 8 (1.8)'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6s
1 actionable task: 1 executed
==> ERROR: A failure occurred in build().
    Aborting...
error making: signal-cli

Any hints?

daniel.sch commented on 2020-10-20 14:00

@fruitywelsh: The fix for this problem is to run

archlinux-java set java-11-openjdk

(see https://wiki.archlinux.org/index.php/java#Change_default_Java_environment)

fruitywelsh commented on 2020-09-28 06:21

I started to get failing buildings with the error:

* What went wrong:
Execution failed for task ':compileJava'.
> Could not target platform: 'Java SE 11' using tool chain: 'JDK 8 (1.8)'.

I was able to get a successful build in my owned cloned git and install by setting: export JAVA_HOME="/usr/lib/jvm/java-11-openjdk" export PATH="${JAVA_HOME}/bin:${PATH}"

and installing it manually as described in the README

Adding these to lines to lines 29 and 30 in PKGBUILD, succeeds in building, but gives errors when trying to run the command:

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/asamk/signal/Main has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495)

These errors persists even if my env includes the modified JAVA_HOME and PATH

Sorry if this is wrong place to put this, hope this is useful :)

dfroger commented on 2020-09-23 12:27

I can' import the signing key:

> gpg --recv-keys FA10826A74907F9EC6BBB7FC2BA2CD21B5B09570
gpg: keyserver receive failed: General error

Edit: it worked like this:

gpg --keyserver pool.sks-keyservers.net --recv-key FA10826A74907F9EC6BBB7FC2BA2CD21B5B09570