FFmpeg recently changed all the include paths. Every application using it should update. Make sure the applications build against currently hardmasked media-video/ffmpeg-0.4.9_p20080326. video packages left to do: media-libs/libquicktime media-video/dvbcut media-video/dvd-slideshow media-video/dvdrip media-video/ffmpeg2theora media-video/freej media-video/kino media-video/lives media-video/motion media-video/nemesi media-video/noad media-video/tovid media-video/videotrans
already fixed by hd_brummy: media-video/noad
media-video/kino-1.3.0 fixed. Denis.
media-video/dvbcut-0.5.4-r1 fixed.
Please fix by next week: TODO: media-video/ffmpeg2theora - needs patch media-video/lives - update to 0.9.8.12 works (is the only version i tested) media-video/motion - works but disables ffmpeg support even with USE=ffmpeg, because headers are not found media-video/nemesi - is hardmasked anyway, but would need testing Done: media-video/noad media-video/kino media-video/dvbcut media-libs/libquicktime - wfm media-video/dvd-slideshow - just runtime, should work media-video/dvdrip - just runtime, should work media-video/freej - not in portage media-video/tovid - just runtime, should work media-video/videotrans - works
Fixed by version bump to ffmpeg2theora-0.21, lives-0.9.8.12. TODO: motion - there is a new release (3.2.10.1) but this needs updated as-needed patch as well as a patch for new ffmpeg headers location.
(In reply to comment #5) > Fixed by version bump to ffmpeg2theora-0.21, lives-0.9.8.12. ffmpeg2theora-0.21 may build against the hardmasked ffmpeg, but it fails building against latest unstable ffmpeg. I assume that libavdevice is missing. JFYI.
media-libs/libquicktime is not done, it still needs a patch to actually work with new ffmpeg.
*** Bug 228727 has been marked as a duplicate of this bug. ***
*** Bug 228775 has been marked as a duplicate of this bug. ***
media-libs/libquicktime-1.0.2_p20080621 fixes that package, media-video/motion is fixed with version 3.2.10.1. That would leave only nemesi, but that is hardmasked anyway, so I'm closing this bug.
Bug 228775 is still happening for me. Shall I reopen this bug?
(In reply to comment #11) > Bug 228775 is still happening for me. Shall I reopen this bug? With libquicktime-1.0.2_p20080621 ?
Yes: # equery l -p libquicktime [ Searching for package 'libquicktime' in all categories among: ] * installed packages [I--] [ ~] media-libs/libquicktime-1.0.2_p20080621 (0) * Portage tree (/usr/portage) [-P-] [ ] media-libs/libquicktime-1.0.2 (0)
Actually, maybe it's not bug 228775. It looks like media-video/transcode is the problem, not libquicktime: # emerge -avuD world These are the packages that would be merged, in order: Calculating world dependencies - !!! The following installed packages are masked: - dev-util/tla-1.3.5 (masked by: package.mask) /usr/portage/profiles/package.mask: # Jeremy Olexa <darkside@gentoo.org> (3 Jul 2008) # Masked for removal in ~60 days by treecleaners. bug #59548 # dev-util/tla leaks file descriptors. app-emacs/xtla is not usable and depends # on tla. Use >=app-editors/emacs-cvs-23 or app-emacs/dvc (from the Emacs # overlay) as a replacement. | !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: media-video/ffmpeg:0 ('ebuild', '/', 'media-video/ffmpeg-0.4.9_p20070616-r2', 'merge') pulled in by ('ebuild', '/', 'media-video/transcode-1.0.4-r3', 'merge') ('installed', '/', 'media-video/ffmpeg-0.4.9_p20080326', 'nomerge') pulled in by ('installed', '/', 'media-video/dvd-slideshow-0.8.0', 'nomerge') ('ebuild', '/', 'media-libs/xine-lib-1.1.13', 'merge') ('installed', '/', 'media-sound/sox-14.0.1', 'nomerge') (and 7 more)
That's because you're mixing stable and testing branches. Use the ~arch version of transcode (currently 1.0.6_rc2-r1) with the ~arch version of ffmpeg.
So it is. Apologies for the false alarm, and thanks for the help diagnosing my problem.
I think k3b with ffmpeg flag also has some issues. I had to use the ~ branch to get it working.
(In reply to comment #17) > I think k3b with ffmpeg flag also has some issues. I had to use the ~ branch to > get it working. Please report on bug 230151 if that is the case.
