Your message dated Tue, 10 May 2016 13:57:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#823679: nmu: libccaudio2_2.1.3-1.1 libccrtp_2.0.9-2.2 
libzrtpcpp_2.3.4-1.1
has caused the Debian Bug report #823679,
regarding nmu: libccaudio2_2.1.3-1.1 libccrtp_2.0.9-2.2 libzrtpcpp_2.3.4-1.1
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 [email protected]
immediately.)


-- 
823679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823679
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu

Looks like an unnoticed libucommon7v5 -> libucommon8 transition, the new
ucommon is already in testing. Maybe the old one wasn't in testing.

nmu libccaudio2_2.1.3-1.1 . ANY . unstable . -m "Rebuild against ucommon 7.0.0"
nmu libccrtp_2.0.9-2.2 . ANY . unstable . -m "Rebuild against ucommon 7.0.0"
nmu libzrtpcpp_2.3.4-1.1 . ANY . unstable . -m "Rebuild against ucommon 7.0.0"

There is also twinke, but it FTBFS.


Andreas

--- End Message ---
--- Begin Message ---
On 07/05/16 15:41, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
> 
> Looks like an unnoticed libucommon7v5 -> libucommon8 transition, the new
> ucommon is already in testing. Maybe the old one wasn't in testing.
> 
> nmu libccaudio2_2.1.3-1.1 . ANY . unstable . -m "Rebuild against ucommon 
> 7.0.0"
> nmu libccrtp_2.0.9-2.2 . ANY . unstable . -m "Rebuild against ucommon 7.0.0"
> nmu libzrtpcpp_2.3.4-1.1 . ANY . unstable . -m "Rebuild against ucommon 7.0.0"
> 
> There is also twinke, but it FTBFS.

Scheduled.

Thanks,
Emilio

--- End Message ---

Reply via email to