Closed PastCoder closed 2 weeks ago
Please report it to the deb package creator. Not a general issue with signal-cli.
@AsamK I can do, if I know what/where the "deb package creator" is. I have to admit that I am more or less a stupid user of the signal-cli.
@PastCoder: apt-cache policy <package_name>
(the latter is likely signal-cli
) should show you the location of the repository where you downloaded the .deb
package in question. Maybe it's one of the repositories listed under https://github.com/AsamK/signal-cli/wiki/Binary-distributions#linux-packages?
(Alternatively, apt-cache show <package_name>
should directly mention both Homepage:
and Maintainer:
.)
btw, i've added some extra string to the version indicator to make clear the package has been pulled from my repo instead of upstream, so probably future issues like this will be reported to me directly.
signal-cli --version
signal-cli 0.13.6+morph027+4
In updated today via apt update / apt upgrade.
Since then signal-cli reports the following error: