Bug#736150: marked as done (transition: libexosip2)
Your message dated Wed, 02 Jul 2014 12:13:40 +0200
with message-id <53B3DB54.4000705@debian.org>
and subject line Re: Bug#736150: transition: libexosip2
has caused the Debian Bug report #736150,
regarding transition: libexosip2
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.)
--
736150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736150
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: libexosip2
- From: Mark Purcell <msp@debian.org>
- Date: Mon, 20 Jan 2014 21:58:31 +1100
- Message-id: <20140120105831.30395.24282.reportbug@antec.local>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Hi,
Request a transition slot for libexosip2.
Thanks,
Mark
libexosip2-10
Reverse Depends:
libexosip2-10:i386
sipwitch
linphone-nogtk
linphone
liblinphone5
libexosip2-dev
Ben file:
title = "libexosip2";
is_affected = .depends ~ "libexosip2-10" | .depends ~ "libexosip2-11";
is_good = .depends ~ "libexosip2-11";
is_bad = .depends ~ "libexosip2-10";
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: Mark Purcell <msp@debian.org>, 736150-done@bugs.debian.org
- Subject: Re: Bug#736150: transition: libexosip2
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Wed, 02 Jul 2014 12:13:40 +0200
- Message-id: <53B3DB54.4000705@debian.org>
- In-reply-to: <53A02EE0.9070807@debian.org>
- References: <20140120105831.30395.24282.reportbug@antec.local> <20140316183751.GP17725@betterave.cristau.org> <1488205.dYXh8HHlZx@acer> <5384AA75.9030907@debian.org> <5390B6E8.5050308@debian.org> <53A02EE0.9070807@debian.org>
On 17/06/14 14:04, Emilio Pozuelo Monfort wrote:
> On 05/06/14 20:28, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 -confirmed
>>
>> On 27/05/14 17:08, Emilio Pozuelo Monfort wrote:
>>> Control: tags -1 confirmed
>>>
>>> On 20/04/14 08:46, Mark Purcell wrote:
>>>> On Sun, 16 Mar 2014 19:37:52 Julien Cristau wrote:
>>>>> Are there any API changes? Have the reverse deps been build tested?
>>>>
>>>> Julien,
>>>>
>>>> No API changes apparent.
>>>>
>>>> sipwitch binNMU OK
>>>> linphone binNMU OK
>>>>
>>>> Updated Ben file:
>>>>
>>>> title = "libexosip2";
>>>> is_affected = .depends ~ "libosip2-10|libexosip2-10" | .depends ~
>>>> "libosip2-11|libexosip2-11";
>>>> is_good = .depends ~ "libosip2-11|libexosip2-11";
>>>> is_bad = .depends ~ "libosip2-10|libexosip2-10";
>>>
>>> I have updated the tracker (fixing "libfoo|libbar" to /libfoo|libbar/). libosip
>>> brings another rdep, siproxd. Can that one be handled with a binnmu? If so,
>>> please go ahead and upload libexosip and libosip to unstable.
>>
>> Please hold this until after the libgnutls-deb0-28 transition, as they clash and
>> that one is ongoing now.
>
> That's done. You can proceed with this now.
And they are in. Closing.
Emilio
--- End Message ---
Reply to: