Bug#692327: libotr: Please provide libotr2

On Mon, Nov 5, 2012 at 2:36 PM, Julien Cristau <jcristau@debian.org> wrote:

On Mon, Nov 5, 2012 at 11:58:12 +0100, Thibaut VARENE wrote:

> severity 692327 important
> thanks
>
> On Mon, Nov 5, 2012 at 1:32 AM, Dmitrijs Ledkovs <xnox@debian.org> wrote:
>
> > Package: libotr, release.debian.org
> > Severity: serious
> > User: release.debian.org@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.
> >
>
> It was done because upstream has updated their source and the new libotr is
> incompatible with the old one.
>

Which means it's not an appropriate change during a freeze.

I thought that Wheezy having been frozen for quite some time, it was okay to upload new packages to unstable again. Please note in passing that libotr5, being NEW, went through the NEW queue and was reviewed at that time.

>
> > 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:
> >
>
> I was not aware a "coordinated transition" was necessary for such a small
> library. I'm under the impression the release team has bigger fish to fry
> right now.
>

Which is why they very much don't appreciate this kind of disruption.
A SONAME bump in a library right now in sid is not welcome, and needs to
wait until the wheezy release. Please revert.

That wasn't obvious to me. What do you mean "revert"? I cannot upload a package with an older revision.

--
Thibaut VARENE
http://hacks.slashdirt.org/