libotr: Please reintroduce libotr2

Bug #1075016 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libotr (Debian)
Fix Released
Unknown
libotr (Ubuntu)
Fix Released
Undecided
Unassigned
libotr2 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Imported from Debian bug http://bugs.debian.org/692327:

Package: libotr, release.debian.org
Severity: serious
User: <email address hidden>
Usertags: transition

Recently libotr has been updated to version 4.x.x with binary package
name libotr5.

By the looks of things, it was done because of pidgin-otr package which
now requires libotr5.

But this means an un-coordinated transition has started, as there are 6
other packages that build-depend on libotr2-dev and all of them fail to
build from source against libotr5-dev:

* bitlbee
* irssi-plugin-otr
* kdenetwork
* mcabber
* psi-plus
* python-otr

Please do something to resolve this. Input from release team is highly welcome.

Possibilities I can think of are:
* revert libotr source package to 3.2.1-1 & upload libotr5 (4.0.0-2) source package
* keep libotr source package as it is, upload libotr2 (3.2.1-1) source package
* provide patches/NMUs to fix FTBFS for above packages when built
  against libotr5-dev.

Usually disruptive uploads like this one, should be co-ordinated with
the release team with a transition bug, and staged in experimental to do
test rebuilds.

Regards,

Dmitrijs.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Uploading libotr2 as it was at 3.2.1-1 will fix this britney transition:

Trying easy from autohinter: libotr/4.0.0-2 pidgin-otr/4.0.0-1
leading: libotr,pidgin-otr
start: 441+0: i-147:a-89:a-62:a-64:p-79
orig: 441+0: i-147:a-89:a-62:a-64:p-79
easy: 495+0: i-161:a-99:a-72:a-74:p-89
    * i386: bitlbee-plugin-otr, irssi-plugin-otr, kde-full, kde-standard, kdenetwork, kopete, kubuntu-full, mcabber, psi-plus-plugins, psi-plus-plugins-dbg, psi-plus-skins, python-otr, python-otr-dbg, xchat-otr
    * amd64: bitlbee-plugin-otr, irssi-plugin-otr, kopete, kubuntu-full, mcabber, psi-plus-plugins, psi-plus-plugins-dbg, python-otr, python-otr-dbg, xchat-otr
    * armel: bitlbee-plugin-otr, irssi-plugin-otr, kopete, kubuntu-full, mcabber, psi-plus-plugins, psi-plus-plugins-dbg, python-otr, python-otr-dbg, xchat-otr
    * armhf: bitlbee-plugin-otr, irssi-plugin-otr, kopete, kubuntu-full, mcabber, psi-plus-plugins, psi-plus-plugins-dbg, python-otr, python-otr-dbg, xchat-otr
    * powerpc: bitlbee-plugin-otr, irssi-plugin-otr, kopete, kubuntu-full, mcabber, psi-plus-plugins, psi-plus-plugins-dbg, python-otr, python-otr-dbg, xchat-otr

summary: - libotr: Please provide libotr2
+ libotr: Please reintroduce libotr2
Changed in libotr (Debian):
importance: Undecided → Unknown
Changed in libotr (Ubuntu):
status: New → Fix Released
Changed in libotr2 (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libotr2 - 3.2.1-1ubuntu1

---------------
libotr2 (3.2.1-1ubuntu1) raring; urgency=low

  * Resurrect libotr2 in a separate package. Fixes libotr transition &
    uninstallable packages. (LP: #1075016)
 -- Dmitrijs Ledkovs <email address hidden> Mon, 05 Nov 2012 01:06:26 +0000

Changed in libotr2 (Ubuntu):
status: Invalid → Fix Released
Changed in libotr (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.