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

Bug#757917: marked as done (transition: libav11)

Your message dated Thu, 02 Oct 2014 13:13:38 +0200
with message-id <542D3362.1050206@debian.org>
and subject line Re: Bug#757917: transition: libav11
has caused the Debian Bug report #757917,
regarding transition: libav11
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.)


-- 
757917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757917
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,

I would like to upload libav11 to unstable, which requires the
recompilation of any package that links against it. A prerelease for
Libav11 that passes upstream's extensive test suite is currently in
debian/experimental, and I'll make sure that the final release will be
done and uploaded before jessie freeze. Unlike previous transitions,
this should be less painful compared to Libav10 or Libav9, because
Libav11 maintains full source-code compatibility, cf. to the release
announcement:

https://libav.org/news.html:
The API remains backward compatible, so no source changes should be
required in the code that works with Libav 10. We note however, that a
number of obsolete APIs remain deprecated and will be removed in the
future. All users are strongly encouraged to update their code. A work
in progress migration guide can be found at our wiki. If you are still
having difficulty after reading the migration guide, please do not
hesitate to file a report in our Bugzilla. We have a special category
for porting issues.

Proposed ben file:

Affected: .build-depends ~
/lib(avcodec|avformat|avutil|device|filter|avresample)-dev/
Bad: .depends ~
/lib(avcodec55|avformat55|avutil53|device54|filter4|avresample1)/
Good: .depends ~
/lib(avcodec56|avformat56|avutil54|device55|filter5|avresample2)/


Moritz, do you still have the infrastructure and/or scripts that you
used for the libav10 test rebuild so that we can verify that
everything still builds with libav11? I can give it a shot but
unlikely before this weekend. If not, maybe someone else would be
willing to fill in?

-- 
regards,
    Reinhard

--- End Message ---
--- Begin Message --- 
On 30/08/14 16:53, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 12/08/14 13:41, Reinhard Tartler wrote:
>> I would like to upload libav11 to unstable, which requires the
>> recompilation of any package that links against it.
> 
> Go ahead.

This had migrated a while ago but the old libraries were still in testing
because some reverse dependencies hadn't migrated yet. That just happened and
the old libraries are gone, so we can close this.

Emilio

--- End Message ---
Reply to: