Bug#757917: transition: libav11
On 12/08/14 13:41, Reinhard Tartler wrote:
> 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)/
There already is https://release.debian.org/transitions/html/auto-libav.html
This sounds good in principle, but I would like to hear about the results of a
mass-rebuild of the rdeps.
Emilio
> 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?
>
Reply to: