Re: [signal-cli] Seeking committer to merge crucial fix

Hello!

> Hi!
> 
>> Last week I was notified that the current signal-cli in ports bricks users
>> out of signal (possibly losing data, I'm not sure). A version bump was
>> submitted a couple months ago, but has not been looked at yet. It has now
>> been updated to the latest signal-cli.,
>> Would a committer be willing to look at it?
> 
> I had a look, but libsignal still has unresolved crates issues.
> 
> I'm testing with
> 
> make cargo-crates
> 
> now. What about the newer signal-cli and libsignal ? Should
> this be updated to those newer versions ?
> 

See my reply in the bug link for the answer, TLDR they need to be kept 
in lockstep with each other, and an unmerged patch for mautrix-whatsapp.

There is a case for adding multiple versions of libsignal like with 
libsignal-node, however this is not something most applications expect 
(having multiple libsignal available), and would put extra burden on me 
and the committers.

As for the build issues, I was indeed a bit too hasty trying to get 
everything working that I forgot to do my own job. A new patch is availble.

- Jaap

PS Thanks for taking a look :)