[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

This bug was fixed in the package bitlbee - 3.2.1+otr4-1ubuntu0.2 --- bitlbee (3.2.1+otr4-1ubuntu0.2) trusty; urgency=medium * debian/rules: apply the patch manually (LP: #1315550) * debian/patches/series: remove, not needed -- Timo Jyrinki Thu, 22

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Thanks to everyone who helped <3 Really happy to finally be able to consider this completely solved :D -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Got 3.2.1+otr4-1ubuntu0.2, all four tests passing. Everything else seems to be working normally too. ...Is this enough for a SRU verification? Do I just go ahead and change tags now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

@Dx: That's enough, I can mark the tag for you. ** Tags removed: verification-needed ** Tags added: verification-done -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

I agree, I wasn't aware of the magnitude of changes necessary. Would be nice to fix it properly in the future. -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

I think with the debian/rules being the mess it is, the current way of applying a patch manually there (another one, there's an existing one already) would be fine for SRU. I agree the packaging should be improved, but the debian/rules should be rewritten from scratch which is not appropriate for

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

>You need to have an upstream tarball (named e.g. bitlbee_3.4.1.orig.tar.gz) >available in the parent directory. >The 1.0 format falls back to a "native" package if it can't find the upstream >tarball, which is probably not what you want. Uh, well, I don't know what to do with this information.

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

** Changed in: bitlbee (Ubuntu) Importance: Undecided => Medium ** Changed in: bitlbee (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315550

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Would it be possible to actually fix the package so it properly handles quilt patches? Seems like a big hack to have to introduce patches manually in rules like this especially if its already using debhelper. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

There's this pending pull request, which i have no idea what to do with: https://github.com/bitlbee/bitlbee/pull/43 It changes the format from "1.0" to "3.0 (quilt)" and by doing so it breaks the build (it's got a red X from the travis-ci build). Specifically, dpkg-buildpackage throws:

Re: [Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

On Wed, Oct 28, 2015 at 09:06:10PM -, Dx wrote: > There's this pending pull request, which i have no idea what to do with: > https://github.com/bitlbee/bitlbee/pull/43 > > It changes the format from "1.0" to "3.0 (quilt)" and by doing so it > breaks the build (it's got a red X from the

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Thanks! I uploaded 0.2 now to the queue again. I should have asked your for testing a "~test" version the first time too, to catch this without the loop to the distro and back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Huge success! All four test cases in the ticket description are now passing. -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Nope! Same thing! Here, have a command to check if the last part of that function changed: # gdb -q -ex 'disas otr_filter_msg_out+240,+50' -ex q /usr/lib/bitlbee/otr.so Reading symbols from /usr/lib/bitlbee/otr.so...(no debugging symbols found)...done. Dump of assembler code from 0x479e to

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

@Dx: Argh, so it is. And the packaging is also a bit archaic in other ways, so I would just apply the patch manually similar to the config patch. Could you please test the 3.2.1+otr4-1ubuntu0.2~test2 from ppa :timo-jyrinki/quantal-compiz-unity-testing ? (don't mind the PPA name, my normal PPA is

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Third time the charm! If you look at the build log, the patch was applied _after_ the compilation. I now moved it to the beginning of the build phase as it should be. So, please test ~test4 and maybe we soon have SRU:able fix. The packaging would use an overall renewal but for SRU the fewer

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Hello William, or anyone else affected, Accepted bitlbee into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bitlbee/3.2.1+otr4-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

** Branch linked: lp:ubuntu/trusty-proposed/bitlbee -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

3.2.1+otr4-1ubuntu0.1 still segfaults. A disasm at the point of the segfault, near the end of otr_filter_msg_out(), shows that it didn't change. The last few calls are still otrl_message_sending() and g_free(), as opposed to g_strdup(), otrl_message_free() and irc_usernotice() Is this something

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Thanks for caring about the users, Dx! I verified the backported commits seem sane and tested build + briefly started it. I've uploaded it to the queue https://launchpad.net/ubuntu/trusty/+queue?queue_state=1_text= - when it gets approved from there, this bug gets updated with instructions on how

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Oh I should probably expand on the "what's going on": this is still very broken in trusty (even though it says fix released - that's vivid) and we still regularly get users complaining about it every few months. I don't want to keep dealing with the issue for the next few years. Please. -- You

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

** Also affects: bitlbee (Ubuntu Trusty) Importance: Undecided Status: New -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

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,

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Wait. Dammit. Wrong status. Can't set it back. -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

So apparently I can change the status of this issue to fix released (in vivid) ** Changed in: bitlbee (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

vivid has 3.2.2-2, isn't that recent enough? -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Oh thanks jelmer for appearing. #ubuntu-bugs didn't reply ;_; So fix released is okay even if it's just the development version, and the ticket is about trusty and utopic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

** Description changed: The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems in the OTR negotiation phase. These problems have been fixed in the nightlies for bitlbee. Relevant tickets are:

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

** Description changed: The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems in the OTR negotiation phase. These problems have been fixed in the nightlies for bitlbee. Relevant tickets are:

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Updated description to fit the SRU template, and I just noticed that each description change shoots an email. Sorry for that! ** Description changed: The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

3.2.2-2 is in vivid now, arrived a bit too late for utopic :( I'll be looking into what's needed to SRU this -- 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

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

This is fixed in the 3.2.2 release, which introduces proper OTR support. To summarize the issues found and fixed: - crashing when sending messages to contacts with no previous otr context - silently dropping all messages when opportunistic otr is enabled, which is the default mode - receiving a

[Bug 1315550] Re: Current 14.04 bitlbee build using broken OTR (fixed in nightlies)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bitlbee (Ubuntu) Status: New = Confirmed -- 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: