Package: libotr, release.debian.org Severity: serious User: release.debian....@packages.debian.org 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. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vcdkevox....@canonical.com
