Opened 10 years ago

Closed 10 years ago

#44135 closed defect (fixed)

bitlbee @ 3.0.5_2 Build failure with libotr 4

Reported by: downtown@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.0
Keywords: Cc: rsync@…, ryandesign (Ryan Carsten Schmidt)
Port: bitlbee

Description

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.

Attachments (1)

bitlbee_fail.log (82.5 KB) - added by downtown@… 10 years ago.
bitlbee build failure with OTR

Download all attachments as: .zip

Change History (9)

Changed 10 years ago by downtown@…

Attachment: bitlbee_fail.log added

bitlbee build failure with OTR

comment:1 Changed 10 years ago by downtown@…

Cc: downtown@… added

Cc Me!

comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: nomaintainer@… removed
Port: bitlbee added

comment:3 Changed 10 years ago by 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.

comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added; downtown@… removed
Keywords: mavericks removed
Summary: bitlbee @ 3.0.5_2 Build failurebitlbee @ 3.0.5_2 Build failure with libotr 4

comment:5 Changed 10 years ago by 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.

comment:6 in reply to:  5 Changed 10 years ago by 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

comment:7 Changed 10 years ago by tempservice@…

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

comment:8 Changed 10 years ago by pixilla (Bradley Giesbrecht)

Resolution: fixed
Status: newclosed

See r122392

Note: See TracTickets for help on using tickets.