I also support the request for bringing back the ffmpeg *program*.
I think most people (who are not involved in the development and/or package maintenance of libav or ffmpeg; like myself) do not have a strong opinion on which library vlc, chromium or other programs use. It's the decision of the developers and/or package maintainers of those programs which one the use, and it is their responsibility to make sure those programs still work correctly after a switch from one library to another. I dare to say that most users would not even notice. What people do notice, is when their scripts fail because a program they have been using for a long time is "silently" replaced with something else that doesn't work in the (exact) same way. It took me quite some time to figure out what was going on, when I tried to apt-get install ffmpeg on a new machine where I hadn't added deb-multimedia to the repositories yet (which I had on other machines, but for different reasons) and it didn't behave as expected. I had never heard of libav before, and I don't think I completely understand the situation, even after reading http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html and this page (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729203) and I certainly don't want to jump into what seems to be a very hot discussion. On 2014-02-05 07:44, Adrian Bunk wrote:
That was fixed last year September when the ffmpeg packages was removed from unstable.
The confusing *transitional* packages that is. That is certainly better than the current situation in stable, but actually having back ffmpeg (the program) would make almost everyone happy, I believe. Cheers, Dietmar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org