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

Bug#739079: marked as done (transition: libav10)

Your message dated Thu, 29 May 2014 10:10:55 +0200
with message-id <20140529081055.GQ15435@betterave.cristau.org>
and subject line Re: Bug#739079: transition: libav10
has caused the Debian Bug report #739079,
regarding transition: libav10
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.)


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

Hi,

We have a new libav transition pending. Libav 10 is prepared in
debian/experimental, and I've started to build packges against this new
version; in fact, more or more packages require Libav 10 and the new
APIs it provides.

Unfortunately, this new release does break a number of packages in the
debian archive. At upstream, we are concerned about this and have
conducted a survey about the fallout here:
https://etherpad.mozilla.org/mnrZI5XlxP

Most projects have been fixed upstream already, some other are rather
easy to fix (e.g., simple renames such as CODEC_ID -> AV_CODEC_ID,
etc.). In order to help with porting, Libav provides a migration guide here:
https://wiki.libav.org/Migration/10

I sincerly do hope that this libav10 transition will not be as painful
as libav9, but we do have a number of undermaintained packages in the
archive that require upstream work. For those, I'd suggest to be a bit
more aggressive with removing them from testing for the sake of having
this transition done more quickly.

Thanks for your assistance.

Ben file:

title = "libav";
is_affected = .depends ~ /lib(avcodec|avformat|avutil|device|filter)-dev/
is_good = .depends ~ /lib(avcodec55|avformat55|avutil53|device54|filter4)/
is_bad = .depends ~ /lib(avcodec54|avformat54|avutil52|device53|filter3)/


-- System Information:
Debian Release: 7.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11.0-15-generic (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Wed, May 28, 2014 at 05:45:59 +0100, Adam D. Barratt wrote:

> On Tue, 2014-05-27 at 19:54 -0400, Reinhard Tartler wrote:
> > Now that libav transitioned to testing, and
> > https://release.debian.org/transitions/ says '100%' next to the libav
> > transition, what's left to be done here?
> 
> The old libraries need to be removed from testing.
> 
Looks like that's happened now.  Closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: