Debian Bug report logs - #767103
irssi-plugin-otr needs rebuild on new uploads of irssi

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: David Kalnischkies <david@kalnischkies.de>

To: submit@bugs.debian.org

Subject: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Tue, 28 Oct 2014 15:00:40 +0100

[Message part 1 (text/plain, inline)]

Package: irssi-plugin-otr
Version: 1.0.0-1
Severity: grave
X-Debbugs-CC: irssi@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 session.

Doing it now seems to not send anything to the remote user I tried to
init an OTR session with and instead a message like this shows up in the
status window:

14:50:16 [oftc] OTR: Initiating OTR session...
14:50:20 [oftc] -!- H�G(�ff.�: No such nick/channel

OTR inits from the remote end don't trigger any interesting status messages,
but the query window contains the usual "Gone secure" message, but nearly
after every message from the remote (sprinkled in with a message telling me
that this wasn't sent inside the OTR session) and the indicator claims it
is still plaintext. I haven't really investigated which one is true as that
smells fishy either way.

(I think it is unrelated, but for completeness: the remote end is Pidgin,
but a simple webclient as remote doesn't show any message along the lines of
"?OTRv23?" if I try to init either; irssi is connected via ZNC).


Downgrading irssi to the previous version solves this issue.
I have CC'ed irssi maintainers in case they have an idea what is wrong
and/or as this if unsolved effects jessie might warrant a Breaks.


Best regards

David Kalnischkies

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: David Kalnischkies <david@kalnischkies.de>

Cc: 767103@bugs.debian.org

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Tue, 04 Nov 2014 20:14:24 +0100

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,
--
intrigeri

Message #17 received at 767103@bugs.debian.org (full text, mbox, reply):

From: David Kalnischkies <david@kalnischkies.de>

To: 767103@bugs.debian.org

Cc: intrigeri <intrigeri@debian.org>

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Thu, 6 Nov 2014 22:52:10 +0100

[Message part 1 (text/plain, inline)]

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 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. :(

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.
(sorry, I can't test with a real remote at the moment)

Looks like libotr5 still has an ABI break somewhere – or the +b1
happened at the time libotr5 had one, so that it picked it up
accidentally (at least in the amd64 rebuild)?

So, next action is reassigning to release team for another binNMU,
to libotr5 to find the possible regression or … ?


Best regards

David Kalnischkies

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: David Goulet <dgoulet@ev0ke.net>, David Kalnischkies <david@kalnischkies.de>

Cc: 767103@bugs.debian.org

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Fri, 07 Nov 2014 10:15:22 +0100

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 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.

> 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)?

> Looks like libotr5 still has an ABI break somewhere –

I'd be surprised, as several people looked pretty closely and didn't
find one, but well.

> or the +b1 happened at the time libotr5 had one, so that it picked
> it up accidentally (at least in the amd64 rebuild)?

The only relevant change that was reverted in libotr 4.1.0-2 is
a version check that happens at runtime, so I doubt it.

> So, next action is reassigning to release team for another binNMU,
> to libotr5 to find the possible regression or … ?

I'm asking upstream (Cc'd): David (Goulet), may you please have a look
at this bug report?

Cheers,
-- 
intrigeri

Message #27 received at 767103@bugs.debian.org (full text, mbox, reply):

From: David Kalnischkies <david@kalnischkies.de>

To: intrigeri <intrigeri@debian.org>

Cc: David Goulet <dgoulet@ev0ke.net>, 767103@bugs.debian.org

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Sat, 8 Nov 2014 01:12:32 +0100

[Message part 1 (text/plain, inline)]

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 (application/pgp-signature, inline)]

Message #32 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: 767103@bugs.debian.org, David Goulet <dgoulet@ev0ke.net>

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Mon, 10 Nov 2014 12:41:39 +0100

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 that could tie it up more
tightly than e.g. pidgin-otr into the internals of libotr?

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 far as Jessie
is concerned, this might be the way to go.

Cheers,
-- 
intrigeri

Message #37 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 767103@bugs.debian.org

Cc: David Goulet <dgoulet@ev0ke.net>

Subject: Re: [pkg-otr-team] Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Mon, 10 Nov 2014 11:54:53 +0000

[Message part 1 (text/plain, inline)]

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 said, I 
don't expect I will have time for this before the weekend...
 
> 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 far as Jessie
> is concerned, this might be the way to go.

if were doing this I'd suggest to add a versioned dependency...


cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #42 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: 767103@bugs.debian.org

Subject: Re: [pkg-otr-team] Bug#767103: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Mon, 10 Nov 2014 13:12:39 +0100

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 far as Jessie
>> is concerned, this might be the way to go.

> if were doing this I'd suggest to add a versioned dependency...

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 Jessie, and I intend to upload the
latest libotr to wheezy-backports in the next few days (as per Julien
Cristau's suggestion) to avoid similar issues for pidgin-otr.

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.

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.

Message #47 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 767103@bugs.debian.org

Subject: Re: Bug#767103: [pkg-otr-team] Bug#767103: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Mon, 10 Nov 2014 12:22:24 +0000

[Message part 1 (text/plain, inline)]

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 Jessie, and I intend to upload the
> latest libotr to wheezy-backports in the next few days (as per Julien
> Cristau's suggestion) to avoid similar issues for pidgin-otr.

ack
 
> 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 do that? or: whether is an example of such breakage?

> 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...


cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #52 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 767103@bugs.debian.org, Debian OTR Team list <pkg-otr-team@lists.alioth.debian.org>

Subject: Re: [pkg-otr-team] Bug#767103: Bug#767103: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Mon, 10 Nov 2014 15:13:51 +0100

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 do that? or: whether is an example of such breakage?

No idea. I'm only afraid that ${shlibs:Depends} might not override
a (even lower) manually added dependency.

>> 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...

Cool, thanks!

Message #57 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Gerfried Fuchs <rhonda@deb.at>

To: intrigeri <intrigeri@debian.org>, 767103@bugs.debian.org

Cc: David Kalnischkies <david@kalnischkies.de>

Subject: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Thu, 13 Nov 2014 10:34:05 +0100

* intrigeri <intrigeri@debian.org> [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 to 4.1.0-1?

 I'm not so much sure if that has anything to do with libotr API.  irssi
happens to change api/abi every now and then and plugins need to get
recompiled on almost any new irssi release.  I have the same issue with
irssi 0.8.17 from backports and irssi-plugin-otr from stable.  The
plugin needs a tighter dependency on irssi.

 I'm not familiar with how library packaging works, and whether that
could be used at all for irssi, thing is that the plugins (especially
the otr one it seems) need to get recompiled every time a new irssi
upstream release happens.

 Anyone who is willing to dig more into this is very much encouraged to
do so and help out, either for the packaging part to ease that pain, or
with upstream to make it more stable in that respect.  I'm personally
lacking the skills to do that because I haven't digged into any library
packaging work at all, so my whole soname versioning knowledge is sort
of non-existing (and I'm still uncertain if that could help here at all,
if only to produce something that the irssi-plugin-* packages won't be
installable anymore after a new irssi upload).

 Please get the binNMU done for now, and anyone more knowledgeable can
figure out how to deal with that in the future.  Sorry that I forgot to
send a mail about the new upstream release this time.

 Enjoy,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los      |
Fühlst du dich hilflos, geh raus und hilf, los    | Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los    |

Message #62 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: 767103@bugs.debian.org, Gerfried Fuchs <rhonda@deb.at>

Subject: Re: Bug#767103: [pkg-otr-team] Bug#767103: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Sat, 15 Nov 2014 11:38:21 +0100

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 wheezy-backports.
If irssi-plugin-otr from wheezy-backports still works with that
libotr, then this will help confirm that the problem is indeed
unrelated to libotr, but instead caused by the irssi upgrade, as
Rhonda pointed out. Holger, may you please test this?

Another way to confirm the root cause of the problem would be to
rebuild irssi-plugin-otr in testing or sid against:

  * the old libotr (4.0.x)
  * the new irssi (0.8.17-1)

... and test that on testing or sid (that is, with the new libotr and
new irssi installed). Any taker? (I'm not using irssi myself, just
giving a hand on this bug since I'm on the pkg-otr team.)

If any of these two tests works, then I'll be fully convinced that
indeed, this plugin needs to be binNMU'd every time irssi is updated,
and then:

  * we should have irssi-plugin-otr binNMU'd in testing;
  * for Stretch, we'll need to have the discussion that Rhonda started
    about library packaging.

Cheers,
--
intrigeri

Message #67 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 767103@bugs.debian.org

Subject: Re: Bug#767103: [pkg-otr-team] Bug#767103: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17

Date: Sat, 15 Nov 2014 11:46:24 +0100

[Message part 1 (text/plain, inline)]

On Samstag, 15. November 2014, intrigeri wrote:
> Rhonda pointed out. Holger, may you please test this?

definitly not before wednesday...

[signature.asc (application/pgp-signature, inline)]

Message #72 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 767103@bugs.debian.org

Subject: irssi-plugin-otr needs rebuild on new uploads of irssi

Date: Mon, 1 Dec 2014 14:57:49 +0100

[Message part 1 (text/plain, inline)]

severity 767103 important
retitle 767103 irssi-plugin-otr needs rebuild on new uploads of irssi

Hi,

irssi-plugin-otr from bpo works for me with irssi from bpo now and I seem to 
recall someone confirmed this for the sid versions too, thus downgrading the 
bug and retitling accordingly.


cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #89 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 811445@bugs.debian.org

Cc: 767103@bugs.debian.org, 772479@bugs.debian.org

Subject: Re: [pkg-otr-team] Processed: block 767103 with 811445

Date: Wed, 20 Jan 2016 00:53:01 +0100

[Message part 1 (text/plain, inline)]

Hi,

> > block 767103 with 811445
> > block 772479 with 811445

I don't think this is the right relationship, #811445 is not 
blocking these bugs from being fixed, instead, #811445 provides 
a means to in future prevent *such kind of bugs*, but it's 
perfectly possible to close 767103 and 772479 without even 
touching 811445.

Probably it's better to just remove these blocks again. (And 
fix all three bugs :-)


cheers,
	Holger

[Message part 2 (text/html, inline)]

[signature.asc (application/pgp-signature, inline)]

Message #94 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Florian Schlichting <fsfs@debian.org>

To: Holger Levsen <holger@layer-acht.org>, 772479@bugs.debian.org

Cc: 811445@bugs.debian.org, 767103@bugs.debian.org

Subject: Re: Bug#772479: [pkg-otr-team] Processed: block 767103 with 811445

Date: Wed, 20 Jan 2016 09:52:30 +0100

Hi Holger,

On Wed, Jan 20, 2016 at 12:53:01AM +0100, Holger Levsen wrote:
> > > block 767103 with 811445
> > > block 772479 with 811445
> 
> I don't think this is the right relationship, #811445 is not 
> blocking these bugs from being fixed, instead, #811445 provides 
> a means to in future prevent *such kind of bugs*, but it's 
> perfectly possible to close 767103 and 772479 without even 
> touching 811445.

can you elaborate in a little detail just how this can be done? I think
this is not really clear among all involved maintainers, which is why we
haven't seen any progress in the last 12..15 months, and my intention
was to start the discussion and get things moving.

In my understanding, #767103 and #772479 are not about acute breakage
now, but a reminder to implement a system for the future that ensures
that irssi plugins will be binNMU'd whenever irssi changes ABI. For this
to be expressed in package relationships, the irssi package has to expose the
ABI version for the plugin packages to strictly depend on. Of course the
plugin packages could Depend: irssi (>= 0.8.17-1~), irssi (<< 0.8.18),
but that would mean a sourceful upload is needed on new upstream
versions of irssi.

What am I missing / what's your suggestion how to do this?

Florian

Message #99 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: 811445@bugs.debian.org

Cc: 772479@bugs.debian.org, 767103@bugs.debian.org

Subject: Re: Bug#772479: [pkg-otr-team] Processed: block 767103 with 811445

Date: Wed, 20 Jan 2016 14:17:01 +0100

[Message part 1 (text/plain, inline)]

Hi Florian,

On Mittwoch, 20. Januar 2016, Florian Schlichting wrote:
> [...] Of course
> the plugin packages could Depend: irssi (>= 0.8.17-1~), irssi (<< 0.8.18),
> but that would mean a sourceful upload is needed on new upstream
> versions of irssi.

that's exactly how those other two bugs can be fixed without touching #811445 
at all and that's why I think the blocking relation is wrong. It's the better 
fix, sure, but it's not a blocker.


cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #104 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Florian Schlichting <fsfs@debian.org>

To: Holger Levsen <holger@layer-acht.org>, 772479@bugs.debian.org

Cc: 811445@bugs.debian.org, 767103@bugs.debian.org

Subject: Re: Bug#772479: [pkg-otr-team] Processed: block 767103 with 811445

Date: Wed, 20 Jan 2016 14:39:48 +0100

On Wed, Jan 20, 2016 at 02:17:01PM +0100, Holger Levsen wrote:
> On Mittwoch, 20. Januar 2016, Florian Schlichting wrote:
> > [...] Of course
> > the plugin packages could Depend: irssi (>= 0.8.17-1~), irssi (<< 0.8.18),
> > but that would mean a sourceful upload is needed on new upstream
> > versions of irssi.
> 
> that's exactly how those other two bugs can be fixed without touching #811445 
> at all and that's why I think the blocking relation is wrong. It's the better 
> fix, sure, but it's not a blocker.

Right. Feel free to remove the blocks then; my intention was to create
some kind of linkage, not assign blame in any way :-)

Florian

Message #117 received at 767103@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@orangeseeds.org>

To: 767103@bugs.debian.org

Subject: API changes in irssi

Date: Thu, 31 Mar 2016 16:51:26 -0400

[Message part 1 (text/plain, inline)]

this belongs more in the main bug report.

[Message part 2 (message/rfc822, inline)]

From: Antoine Beaupré <anarcat@debian.org>

To: Andreas Beckmann <anbe@debian.org>, 818590@bugs.debian.org, Debian OTR Team list <pkg-otr-team@lists.alioth.debian.org>, 818590@bugs.debian.org, Andrea Lusuardi <uovobw@gmail.com>, intrigeri <intrigeri@debian.org>

Subject: Re: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

Date: Thu, 31 Mar 2016 16:46:22 -0400

On 2016-03-18 21:34:43, Andreas Beckmann wrote:
> On Fri, 18 Mar 2016 16:09:45 +0100 intrigeri <intrigeri@debian.org> wrote:
>> Someone (who can first verify that this would fix the problem) should
>> get a binNMU scheduled, I guess :)
>
> While this would probably make the package installable again, this is
> not the proper fix. Next bump and this happens again.
>
> irssi needs to arrange to provide a virtual package, e.g. irssi-abi-1
> and must ensure that plugins pick up a proper dependency on this virtual
> package. Once the abi changes (and the virtual package is renamed), this
> will visibly trigger a transition.
>
> There are several packages in the archive doing this, I think proftpd is
> one of them.

Thinking more about this, I am not sure this will be necessary. There is
an effort underway to merge OTR in the main irssi package, and there are
only two other irssi plugins out there, so I am not sure this is worth
the effort.

Surely this is a bug that should be reported against irssi in any case.

A.

-- 
Evil exists to glorify the good. Evil is negative good.
It is a relative term. Evil can be transmuted into good.
What is evil to one at one time,
becomes good at another time to somebody else.
                        - Sivananda

Message #132 received at 767103@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: 767103@bugs.debian.org

Subject: Re: Bug#767103: irssi-plugin-otr needs rebuild on new uploads of irssi

Date: Fri, 15 Feb 2019 10:15:04 +0100

Control: fixed -1 1.2.0-1

Hi,

I think this bug is moot given the irssi-plugin-otr binary package is
now built from src:irssi.

Cheers,
-- 
intrigeri

Message #139 received at 767103-done@bugs.debian.org (full text, mbox, reply):

From: Rhonda D'Vine <rhonda@deb.at>

To: intrigeri <intrigeri@debian.org>, 767103-done@bugs.debian.org

Subject: Re: Bug#767103: irssi-plugin-otr needs rebuild on new uploads of irssi

Date: Fri, 15 Feb 2019 10:43:40 +0100

    Hey,

 right, thanks for noticing.  I meant to go over the bugreports but then
forgot about it. :)

 Cheers, and thanks for all your work so far!
Rhonda

On 2/15/19 10:15 AM, intrigeri wrote:
> Control: fixed -1 1.2.0-1
> 
> Hi,
> 
> I think this bug is moot given the irssi-plugin-otr binary package is
> now built from src:irssi.
> 
> Cheers,
> 

Send a report that this bug log contains spam.