1. Forum
  2. USENET
  3. muc.lists.freebsd.ports

  • [signal-cli] Seeking committer to merge crucial fix

    From Jaap Aart@jaap.aarts1@gmail.com to muc.lists.freebsd.ports on Mon Apr 6 12:49:48 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hello all,

    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?

    patch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293378
    bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294223

    I am fine with long wait times, but as this hinders users' use of signal
    I feel a moral duty to ask.

    - Jaap Aarts


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Kurt Jaeger@pi@freebsd.org to muc.lists.freebsd.ports on Mon Apr 6 21:31:07 2026
    From Newsgroup: muc.lists.freebsd.ports

    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 ?
    --
    pi@FreeBSD.org +49 171 3101372 Now what ?


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Jaap Aart@jaap.aarts1@gmail.com to muc.lists.freebsd.ports on Mon Apr 6 21:46:24 2026
    From Newsgroup: muc.lists.freebsd.ports


    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 :)


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Philipp@satanist+freebsd@bureaucracy.de to muc.lists.freebsd.ports on Wed Apr 29 23:31:44 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi all
    [2026-04-06 12:49] Jaap Aart <jaap.aarts1@gmail.com>
    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?

    patch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293378
    bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294223

    I am fine with long wait times, but as this hinders users' use of signal > I feel a moral duty to ask.
    Can someone look again on this bug?
    After the last mail there where some traction on the bug, but now it's
    stuck again. I have tried building it myself, but failed at building rust
    on my machine.
    Philipp
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Andrea Venturoli@ml@netfence.it to muc.lists.freebsd.ports on Thu Apr 30 15:59:16 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 4/29/26 23:31, Philipp wrote:

    patch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293378

    FWIW, I applied this to my poudriere port tree and signal-cli has
    started working again.

    bye
    av.


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2