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)
** Bug watch added: BitlBee Bug Tracker #1109
http://bugs.bitlbee.org/bitlbee/ticket/1109
** Bug watch added: BitlBee Bug Tracker #1110
http://bugs.bitlbee.org/bitlbee/ticket/1110
** Patch added: "Backport bitlbee-plugin-otr bug fixes to 3.2.1+otr4-1"
https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/1315550/+attachment/4478209/+files/bitlbee-3.2.1%2Botr4-1-otr-bugfixes.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315550
Title:
Current 14.04 bitlbee build using broken OTR (fixed in nightlies)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/1315550/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
