[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#660034: marked as done (transition: libvpx)

Your message dated Sat, 3 Mar 2012 11:53:19 +0100
with message-id <20120303105319.GJ6969@mraw.org>
and subject line Re: Bug#660034: transition: libvpx
has caused the Debian Bug report #660034,
regarding transition: libvpx
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.)


-- 
660034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660034
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: pending
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

this transition was started by the libvpx upload to unstable replacing
libvpx0 with libvpx1, without any coordination AFAICT:
  http://packages.qa.debian.org/libv/libvpx/news/20120202T163438Z.html

I set up a tracker accordingly:
  http://release.debian.org/transitions/html/libvpx.html

Since this interferes with x264, I'm taking the liberty of 0-day NMUing
it to fix #658453, so that packages involved in the x264 transition can
migrate faster.

BinNMUs for other packages will be needed, too.

I'll fix the submitter address once I have the bug number.

Mraw,
KiBi.

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (15/02/2012):
> this transition was started by the libvpx upload to unstable replacing
> libvpx0 with libvpx1, without any coordination AFAICT:
>   http://packages.qa.debian.org/libv/libvpx/news/20120202T163438Z.html

libvpx0 is finally gone from testing.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: