On Samstag, 15. November 2014, intrigeri wrote:
> Rhonda pointed out. Holger, may you please test this?
definitly not before wednesday...
signature.asc
Description: This is a digitally signed message part.
Hi,
Holger Levsen wrote (10 Nov 2014 12:22:24 GMT) :
>> Also, it would be good if someone tried current libotr (backported to
>> Wheezy) + wheezy-backports' irssi-plugin-otr. I'd hate to break that
>> one when I upload the backport.
> i can test that...
I've just uploaded the latest libotr to wh
* intrigeri [2014-11-04 20:14:24 CET]:
> 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 t
Holger Levsen wrote (10 Nov 2014 12:22:24 GMT) :
>> Anyway, if we do that, for future-proofness you'll want to make sure
>> that the manually added versioned dependency doesn't interfere badly
>> with ${shlibs:Depends} in case that one returns a dependency on
>> a newer version of libotr.
> how to
Hi,
On Montag, 10. November 2014, intrigeri wrote:
> I don't think that (and the corresponding source upload) is needed,
> since the main libotr binary package was renamed from Wheezy to Jessie
> (libotr2 -> libotr5), so the only remaining problematic partial
> upgrade case is wheezy+backports to
Holger Levsen wrote (10 Nov 2014 11:54:53 GMT) :
> On Montag, 10. November 2014, intrigeri wrote:
>> Shall we ask the release team for a binNMU of irssi-plugin-otr, and
>> postpone understanding the root cause of the bug? I'm concerned that
>> it may occur again each time we upgrade libotr, but as
Hi,
On Montag, 10. November 2014, intrigeri wrote:
> I don't care enough about irssi-plugin-otr to dig further into that
> bug. I don't understand how this can possibly break. Can anyone
> reproduce this RC bug and look into it?
yes, it's on my radar and todo list as a user of that plugin. That s
Dear team-mates,
I don't care enough about irssi-plugin-otr to dig further into that
bug. I don't understand how this can possibly break. Can anyone
reproduce this RC bug and look into it?
It might be an unspotted ABI breakage in libotr, who knows. David,
does irssi-plugin-otr do anything strange
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 b
Hi,
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
Hi,
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 a
Control: tag -1 + moreinfo
Hi,
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?
Cheers,
Package: irssi-plugin-otr
Version: 1.0.0-1
Severity: grave
X-Debbugs-CC: ir...@packages.debian.org
Hello!
Upgrading irssi from 0.8.16-1+b1 to 0.8.17-1 seems to break the OTR
plugin for me. Opening a new query window and executing "/otr init"
resulted usually in the initialisation of an OTR sessio
13 matches
Mail list logo
