Comment 9 for bug 1315550

Revision history for this message
dx (dx) wrote :

02:07 < ScottK> If you know how to fix it, attach the patch to a bug, explain what's going on and subscribe the ubuntu-sponsors team to the bug.
02:08 < ScottK> All the distro specific specific bureaucracy they should be able to handle.
02:10 < dx> there are several bugs (i think three of them, two critical, one not so much), is it okay if i submit a single patch with the three of them?
02:12 < Logan> yes

So here it is. It was four bugs, three critical (message loss, crash, crash), one not so much (otr connect is a no-op)

Log message:

    Backport bitlbee-plugin-otr bug fixes to 3.2.1+otr4-1

    Includes the following git commits, slightly adapted to apply cleanly
    after removing a commit that was a failed fix attempt.

    367ea3c: work around libotr 4 not sending outgoing plaintext messages
    329f9fe: use OTRL_INSTAG_BEST instead of _RECENT to work around a segfault in libotr
    74c9e7f: fix a segfault when otr-coloring /me messages
    820a2a7: fix 'otr connect' command

    Relevant bugs:

    - https://bugs.bitlbee.org/bitlbee/ticket/1109
    - https://bugs.bitlbee.org/bitlbee/ticket/1110
    - https://bugs.otr.im/issues/16 (not fixed, but workarounded here)