Your message dated Mon, 5 Nov 2012 20:50:01 +0100 with message-id <20121105195001.GY17465@radis.cristau.org> and subject line Re: Bug#692327: libotr: Please provide libotr2 has caused the Debian Bug report #692327, regarding libotr: Please provide libotr2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 692327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692327 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libotr: Please provide libotr2
- From: Dmitrijs Ledkovs <xnox@debian.org>
- Date: Mon, 05 Nov 2012 00:32:14 +0000
- Message-id: <[🔎] 87vcdkevox.fsf@canonical.com>
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. 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.
--- End Message ---
--- Begin Message ---
- To: Thibaut VARENE <varenet@parisc-linux.org>, 692327-done@bugs.debian.org
- Cc: Dmitrijs Ledkovs <xnox@debian.org>
- Subject: Re: Bug#692327: libotr: Please provide libotr2
- From: Julien Cristau <jcristau@debian.org>
- Date: Mon, 5 Nov 2012 20:50:01 +0100
- Message-id: <20121105195001.GY17465@radis.cristau.org>
- In-reply-to: <[🔎] 20121105133554.GA16380@crater2.logilab.fr>
- References: <[🔎] 87vcdkevox.fsf@canonical.com> <[🔎] CA+DQjFgZn-=8EY6PUmfTPmoy3ajShvL7TLbskrfRAEKnEgG7tg@mail.gmail.com> <[🔎] 20121105133554.GA16380@crater2.logilab.fr>
On Mon, Nov 5, 2012 at 14:36:01 +0100, Julien Cristau wrote: > Please revert. > Nevermind. As the -dev package name has changed and the reverse deps can still use libotr2-dev the current situation should be ok. Assuming ftpmaster doesn't try to remove the NBS packages before release. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---