News for hackers. Stuff that matters.
Re:Why Debian returned to FFmpeg by _delirium on Saturday July 25, 2015 @01:27PM (#9948265)
> It's entirely possible to maintain both packages in Debian with the alternatives framework.

The Debian security team vetoed this option, which is why the recent discussion was choosing between, 1) bring back ffmpeg and remove libav, or 2) keep libav and do not bring back ffmpeg (option 1 was chosen). They don't want to support security patches for both, and for all combinations of software that might use either one.

Re:Why Debian returned to FFmpeg by zimbatm on Saturday July 25, 2015 @02:16PM (#9948446)
Good point. Reality is more fine-grained than the account of my own perception.

Do you know if contrib packages are also getting security updates ? If no then why didn't they just move the ffmpeg package there. To me it felt like the really wanted the ffmpeg package to be virtual and pointing to libav.

Re:Why Debian returned to FFmpeg by yrro on Sunday July 26, 2015 @05:51AM (#9950639)
contrib is not for unsupported packages. It is for free software that depends on non-free software.
Re:Why Debian returned to FFmpeg by listic on Saturday July 25, 2015 @01:33PM (#9948279)
> The Debian security team vetoed this option

On what grounds?

Re:Why Debian returned to FFmpeg by _delirium on Saturday July 25, 2015 @01:38PM (#9948296)
The high frequency of security issues in both packages makes it a significant burden to support both of them simultaneously: https://lists.debian.org/debian-devel/2014/02/msg00668.html

There appear to also be issues with frequent soname bumps: https://lists.debian.org/debian-devel/2014/02/msg00651.html

Re:Why Debian returned to FFmpeg by davidgerard on Sunday July 26, 2015 @09:38AM (#9951012)
This is answered in the article this post is about.