bitlbee @ 3.0.5_2 Build failure with libotr 4

[downtown@…]

otr.c:388:20: error: too few arguments to function call, expected 12, have 11

Errors start piling up at line 767 in the attached log file. It appears to be related to OTR, as building with -otr works fine.

I see there is no package maintainer, so I included the maintainer of libotr as that port is likely involved.

[downtown@…]

bitlbee build failure with OTR

[downtown@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

bitlbee is not compatible with libotr 4.

The bitlbee port is outdated; however, updating to 3.2.1 (#41908) does not fix it.

This was reported upstream in October 2012 and marked fixed in December 2013 (​http://bugs.bitlbee.org/bitlbee/ticket/1004), but no new release of bitlbee containing the fix has been forthcoming.

Please write to the developers of bitlbee to request that they release a new version containing this fix.

[downtown@…]

According to a ticket (​http://bugs.bitlbee.org/bitlbee/ticket/1135) marked notabug, libotr 4 support is fixed in current development release, which is available at ​http://code.bitlbee.org/tarballs. Anything over 1011 includes the OTR for libotr 4 fix.

There is no planned official release date according to those in the channel #bitlbee on OFTC.

[dbevans (David B. Evans)]

Replying to downtown@…:

According to a ticket (​http://bugs.bitlbee.org/bitlbee/ticket/1135) marked notabug, libotr 4 support is fixed in current development release, which is available at ​http://code.bitlbee.org/tarballs. Anything over 1011 includes the OTR for libotr 4 fix.

There is no planned official release date according to those in the channel #bitlbee on OFTC.

According to ​​http://bugs.bitlbee.org/bitlbee/ticket/1004, ​this patch applied to bitlbee 3.2.1 should fix the problem

[tempservice@…]

bitlbee 3.2.2 has been released, which has a patch for this problem.

[pixilla (Bradley Giesbrecht)]

See r122392