On Fri, Nov 07, 2014 at 10:15:22AM +0100, intrigeri wrote: > David Kalnischkies wrote (06 Nov 2014 21:52:10 GMT) : > > On Tue, Nov 04, 2014 at 08:14:24PM +0100, intrigeri wrote: > >> David Kalnischkies wrote (28 Oct 2014 14:00:40 GMT) : > >> > Upgrading irssi from 0.8.16-1+b1 to 0.8.17-1 seems to break the OTR > >> > plugin for me. > >> > >> I'm wondering if this could be a side-effect of #767230. > >> Can you reproduce this after upgrading libotr5 to 4.1.0-1? > > > Sounds like it and I had some hope, but trying with: > > > irssi 0.8.17-1 > > irssi-plugin-otr 1.0.0-1+b1 (+b1 for rebuild against libgcrypt20) > > libgcrypt20:amd64 1.6.2-4 > > libgcrypt20:i386 1.6.2-4 > > libotr5 4.1.0-2 > > > I still have this problem. :( > > OK, thanks.
Just to highlight, you asked for 4.1.0-_1_, but I am at -_2_ – which according to the changelog is the first one with the symbols file. > > I see that irssi-plugin-otr has an unversioned dependency on libotr5. > > Doing an "apt-get source irssi-plugin-otr -b" results in a package with > > a versioned dependency "libotr5 (>= 4.0.0)" and after installing and > > restarting irssi I can run "/otr init" without the mentioned error message > > and the remote gets the '?OTRv23?', so that looks about right. > > Can you confirm you've built it against libotr from sid (that > introduces a proper symbols file)? Yes, libotr5-dev is at 4.1.0-2 just as libotr5. After all the -dev package has an equal-dependency on the library, so my beloved apt would be pretty pissed if it would be at an earlier version. ;) Best regards David Kalnischkies
signature.asc
Description: Digital signature
