Re: libav_0.6.2-1_i386.changes is NEW
Hi Reinhard, thanks for the insightful summary! In related news, I have read that CrystalHD support has now been merged into ffmpeg and mplayer: http://intr.overt.org/blog/?p=125 If this has also already been done in libav, then you really need to advertise yourself a bit more. ;) - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: libav_0.6.2-1_i386.changes is NEW
On Mon, Mar 28, 2011 at 09:06:46 (CEST), Fabian Greffrath wrote: Hi Reinhard, thanks for the insightful summary! BTW, the Libav announcement is now online: http://libav.org/about.html In related news, I have read that CrystalHD support has now been merged into ffmpeg and mplayer: http://intr.overt.org/blog/?p=125 If this has also already been done in libav, then you really need to advertise yourself a bit more. ;) Well, I don't have the hardware to test the patch, but I'll make sure that we'll have it for Libav 0.7. Currently the patch is pending AFAIUI. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: libav_0.6.2-1_i386.changes is NEW
On Fri, Mar 25, 2011 at 10:50:02 (CET), fab...@greffrath.com wrote: Honestly, I still don't get it. Is libav merging from ffmpeg or the other way round? I have just read that ffmpeg has merged ffmpeg-mt, but could not find such an announcement from libav yet. If the two projects merge back and forth anyway, why is there a need for two separate code bases? Yeah, I agree that this is terribly confusing and Libav should finally get the planned About Libav clarification out. A (arguably large) number of FFmpeg developers felt very unhappy about the way how FFmpeg is driven and managed in general and the project leader in particular. Many attempts to resolve and reconcile the issues internally have been attempted but unfortunately, each of them have failed. Therefore, these developer had no other option than properly forking, something that many have (both FFmpeg developers and outsiders such as users, etc.) requested. FFmpeg currently has no single release manager. I'm in very close contact with Libav developers and will continue to drive releases there. For Debian, I think this constitutes an invaluable asset, that's why I have uploaded Libav. And does the original ffmpeg project now use the ffmpeg.org name space that has been initially set up by the fork now called libav? Exactly. The DNS has moved, and the server (natsuki.mplayerhq.hu) that has served ffmpeg.org before is now hosting libav.org. Most of the technical infrastructure, such as mailing list, bug tracker, fate.libav.org, etc. remains on natsuki to serve libav.org. What we see now is that FFmpeg is acting IMO in a pretty panic driven way. With no release manager, no release roadmap or any kind of vision, many very confusing merges in git (from ffmpeg-mt and libav.org) and lots of reverts, I really think Debian is much better off with Libav. Regarding the ffmpeg-mt: This is yet another pretty political move (and one that I personally find quite offensive, BTW). Fact is that ffmpeg supported multi threading for quite some time, what's new is a) infrastructure for slice based multi threading and b) porting of codecs to use that infrastructure. Libav has merged most of the ffmpeg-mt branch long before FFmpeg (way before Libav.org went online) but failed to make a public fuzz about it. What is missing are multi threaded h264, h263, etc. codecs, which is currently worked on (and I marked that release blocker for 0.7). They haven't been merged yet because they break the regression tests. Michael vetoed ffmpeg-mt for years because of that. Now, he has merged it without any public coordination. - Fabian PS: And I already have a *bit* of insight. What do you think how puzzled other users/packagers/potential contributors are?! As indicated above, there is a clarification from the Libav side pending that will hopefully clear up many things. The situation isn't that bad as it seems. There is a considerable amount of code exchange between the two projects (just check the commit mailing lists), and what's most important for us downstreams: The competition that has arisen now has speeded up the development of user visible features, such as the merge of ffmpeg-mt, a lot. Which I think is great news! -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: libav_0.6.2-1_i386.changes is NEW
Reinhard, are there any *technical* reasons for our switch from ffmpeg to the libav fork? What are the technical differences now and in the long term? Will libav retain ABI-/API-compatibility with ffmpeg? - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: libav_0.6.2-1_i386.changes is NEW
On Mon, Mar 21, 2011 at 09:39:22 (CET), Fabian Greffrath wrote: are there any *technical* reasons for our switch from ffmpeg to the libav fork? Well, for the 0.6.2 release, you could argue that it doesn't matter a lot, since there are effectively only two releavant patches included from the 0.6.1 release. What are the technical differences now and in the long term? Will libav retain ABI-/API-compatibility with ffmpeg? This remains to be seen. At the moment and AFAIUI, it is questionable if there will be future FFmpeg releases at all. Michael Niedermayer has asked me last saturday if I would be willing to continue to do FFmpeg releases. I didn't answer yet but asked for a few more days to think it over. In any case, Michael confirmed to me in the same irc query that he will try to stay API/ABI compatible with Libav. In the Libav camp, there are not direct plans to willingfully break API/ABI as well. For large scale distribution like Debian, Libav has clear advantages over FFmpeg: - reliable release process - friendly and receptive upstream - actively maintained regression test suite (FATE) - maintainer (i.e., me) active in upstream Moreover, Libav is currently working to setup a bugzilla instance, which will make forwarding bugs much easier because in contrast to roundup and trac (which is what FFmpeg now uses), allows proper version tracking. I hope this suffices as explanation. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
libav_0.6.2-1_i386.changes is NEW
ffmpeg-dbg_0.6.2-1_i386.deb to main/liba/libav/ffmpeg-dbg_0.6.2-1_i386.deb ffmpeg-doc_0.6.2-1_all.deb to main/liba/libav/ffmpeg-doc_0.6.2-1_all.deb ffmpeg_0.6.2-1_i386.deb to main/liba/libav/ffmpeg_0.6.2-1_i386.deb (new) libav-dbg_0.6.2-1_i386.deb extra debug Debug symbols for Libav related packages This package contains debug data of the Libav related shared libraries. . Most people will not need this package. Please install it to produce useful stacktraces to help debugging the Libav library. (new) libav-doc_0.6.2-1_all.deb optional doc Documentation of the Libav API This package contains the html doxygen documentation of the Libav API. . Only application developers will find this package useful. (new) libav-source_0.6.2-1_all.deb optional devel Patched Libav sources This package contains a tarball the source file that were used to produce this package, containing all modifications that have been applied inline. . This package is used as build-dependency for 'libav-extra', which provides the extra variants of libav. (new) libav_0.6.2-1.diff.gz optional libs (new) libav_0.6.2-1.dsc optional libs (new) libav_0.6.2.orig.tar.gz optional libs libavcodec-dev_0.6.2-1_i386.deb to main/liba/libav/libavcodec-dev_0.6.2-1_i386.deb libavcodec52_0.6.2-1_i386.deb to main/liba/libav/libavcodec52_0.6.2-1_i386.deb libavdevice-dev_0.6.2-1_i386.deb to main/liba/libav/libavdevice-dev_0.6.2-1_i386.deb libavdevice52_0.6.2-1_i386.deb to main/liba/libav/libavdevice52_0.6.2-1_i386.deb libavfilter-dev_0.6.2-1_i386.deb to main/liba/libav/libavfilter-dev_0.6.2-1_i386.deb libavfilter1_0.6.2-1_i386.deb to main/liba/libav/libavfilter1_0.6.2-1_i386.deb libavformat-dev_0.6.2-1_i386.deb to main/liba/libav/libavformat-dev_0.6.2-1_i386.deb libavformat52_0.6.2-1_i386.deb to main/liba/libav/libavformat52_0.6.2-1_i386.deb libavutil-dev_0.6.2-1_i386.deb to main/liba/libav/libavutil-dev_0.6.2-1_i386.deb libavutil50_0.6.2-1_i386.deb to main/liba/libav/libavutil50_0.6.2-1_i386.deb libpostproc-dev_0.6.2-1_i386.deb to main/liba/libav/libpostproc-dev_0.6.2-1_i386.deb libpostproc51_0.6.2-1_i386.deb to main/liba/libav/libpostproc51_0.6.2-1_i386.deb libswscale-dev_0.6.2-1_i386.deb to main/liba/libav/libswscale-dev_0.6.2-1_i386.deb libswscale0_0.6.2-1_i386.deb to main/liba/libav/libswscale0_0.6.2-1_i386.deb Changes: libav (4:0.6.2-1) unstable; urgency=medium . [ Reinhard Tartler ] * Imported Upstream version 0.6.2 - include security fixes (Closes: #611495) * rename source package to libav * Switch to libav packages * copy in changelog entries from the 0.5 packaging branch (Closes: #616190) * update version numbering * make buildlogs verbose * Introduce 'libav-source', which contains the patched sources of libav * rename source package to libav . [ Fabian Greffrath ] * Fix cp of doxy documentation fails with Argument list too long (Closes: #618679) Override entries for your package: ffmpeg-dbg_0.6.2-1_i386.deb - extra debug ffmpeg-doc_0.6.2-1_all.deb - optional doc ffmpeg_0.6.2-1_i386.deb - optional video libavcodec-dev_0.6.2-1_i386.deb - optional libdevel libavcodec52_0.6.2-1_i386.deb - optional libs libavdevice-dev_0.6.2-1_i386.deb - optional libdevel libavdevice52_0.6.2-1_i386.deb - optional libs libavfilter-dev_0.6.2-1_i386.deb - optional libdevel libavfilter1_0.6.2-1_i386.deb - optional libs libavformat-dev_0.6.2-1_i386.deb - optional libdevel libavformat52_0.6.2-1_i386.deb - optional libs libavutil-dev_0.6.2-1_i386.deb - optional libdevel libavutil50_0.6.2-1_i386.deb - optional libs libpostproc-dev_0.6.2-1_i386.deb - optional libdevel libpostproc51_0.6.2-1_i386.deb - optional libs libswscale-dev_0.6.2-1_i386.deb - optional libdevel libswscale0_0.6.2-1_i386.deb - optional libs Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 611495 616190 618679 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
