Package Details: signal-cli 0.13.12-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: GPL-3.0-only
Submitter: AsamK
Maintainer: AsamK
Last Packager: AsamK
Votes: 32
Popularity: 0.002884
First Submitted: 2016-04-02 11:44 (UTC)
Last Updated: 2025-01-18 20:15 (UTC)

Dependencies (7)

Sources (3)

Pinned Comments

AsamK commented on 2017-06-17 12:24 (UTC) (edited on 2021-12-12 15:31 (UTC) by AsamK)

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

« First ‹ Previous 1 2 3 4 5 Next › Last »

atomicfs commented on 2023-04-12 21:52 (UTC)

Hi, I just tried to build the new version, but I am getting following error:

$ makepkg --sign --syncdeps --noconfirm PKGBUILD
==> Making package: signal-cli 0.11.8-1 (Wed Apr 12 21:44:10 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v0.11.8.tar.gz
  -> Found v0.11.8.tar.gz.asc
  -> Found signal-cli.sh
==> Validating source files with sha512sums...
    v0.11.8.tar.gz ... Passed
    v0.11.8.tar.gz.asc ... Skipped
    signal-cli.sh ... Passed
==> Verifying source file signatures with gpg...
    v0.11.8.tar.gz ... Passed
==> Extracting sources...
  -> Extracting v0.11.8.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Error opening zip file or JAR manifest missing : /usr/share/java/gradle/lib/agents/gradle-instrumentation-agent-8.1.jar
Error occurred during initialization of VM
agent library failed to init: instrument
==> ERROR: A failure occurred in build().
    Aborting...

And I am not sure how to fix it, gradle is installed community/gradle 8.1-1 [installed].

fauno commented on 2022-11-12 14:18 (UTC)

signal-cli work with a headless JRE

From 9d2294586031983c3a9e3b41cd524f3e71415d22 Mon Sep 17 00:00:00 2001
From: fauno <fauno@endefensadelsl.org>
Date: Sat, 12 Nov 2022 11:10:45 -0300
Subject: [PATCH] Change dependency to headless JRE

---
 PKGBUILD | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PKGBUILD b/PKGBUILD
index 54302b2..47aee21 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,7 +7,7 @@ pkgdesc="Provides a commandline and dbus interface for secure Signal messaging."
 arch=('any')
 url="https://github.com/AsamK/signal-cli"
 license=('GPL3')
-depends=('java-runtime>=17' 'java-commons-logging' 'sh' 'libsignal-client')
+depends=('java-runtime-headless>=17' 'java-commons-logging' 'sh' 'libsignal-client')
 makedepends=('java-environment>=17' 'gradle' 'asciidoc')
 source=("https://github.com/AsamK/${pkgname}/archive/v${pkgver}.tar.gz"
         "https://github.com/AsamK/${pkgname}/releases/download/v${pkgver}/v${pkgver}.tar.gz.asc"
-- 
2.37.3

dpflug commented on 2022-10-03 18:21 (UTC)

I'm not sure how useful it is having this up to date, considering neither client implementation supports 0.11 yet.

wandinstallation commented on 2022-02-06 10:18 (UTC)

Hi! Since the latest update I get the following error:


Failed to load native library:sqlite-3.36.0.3-82bcdb1f-db06-49a3-b2ad-d852c01fd021-libsqlitejdbc.so. osinfo: Linux/x86_64
java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.36.0.3-82bcdb1f-db06-49a3-b2ad-d852c01fd021-libsqlitejdbc.so: /tmp/sqlite-3.36.0.3-82bcdb1f-db06-49a3-b2ad-d852c01fd021-libsqlitejdbc.so: failed to map segment from shared object
ERROR HikariPool - HikariPool-1 - Exception during pool initialization.
java.sql.SQLException: Error opening connection
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:244)
        at org.sqlite.SQLiteConnection.<init>(SQLiteConnection.java:61)
        at org.sqlite.jdbc3.JDBC3Connection.<init>(JDBC3Connection.java:28)
        at org.sqlite.jdbc4.JDBC4Connection.<init>(JDBC4Connection.java:21)
        at org.sqlite.JDBC.createConnection(JDBC.java:115)
        at org.sqlite.JDBC.connect(JDBC.java:90)
        at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
        at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
        at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
        at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
        at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:100)
        at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
        at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:92)
        at org.asamk.signal.manager.storage.Database.init(Database.java:30)
        at org.asamk.signal.manager.storage.SignalAccount.lambda$getDatabase$17(SignalAccount.java:888)
        at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1114)
        at org.asamk.signal.manager.storage.SignalAccount.getDatabase(SignalAccount.java:886)
        at org.asamk.signal.manager.storage.SignalAccount.initDatabase(SignalAccount.java:236)
        at org.asamk.signal.manager.Manager.init(Manager.java:70)
        at org.asamk.signal.App.loadManager(App.java:361)
        at org.asamk.signal.App.handleLocalCommand(App.java:291)
        at org.asamk.signal.App.init(App.java:211)
        at org.asamk.signal.Main.main(Main.java:58)
Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=x86_64, paths=[/org/sqlite/native/Linux/x86_64:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib]
        at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:389)
        at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68)
        at org.sqlite.core.NativeDB.load(NativeDB.java:63)
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:240)
        ... 23 common frames omitted
Error loading state file for user +myphonenumber: Failed to initialize pool: Error opening connection (PoolInitializationException)

How can I solve this error message? Thanks!

atcw commented on 2022-01-29 01:36 (UTC)

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 (UTC) (edited on 2021-12-12 13:56 (UTC) by stas-t)

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 (UTC)

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 (UTC) (edited on 2021-07-01 07:38 (UTC) by the_10)

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 (UTC)

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 (UTC) (edited on 2021-01-28 14:10 (UTC) by PhotonX)

Same problem as rixx here.