Bug 901755 - kino for fc16/fc17, ffmpeg2dirac for fc17
Summary: kino for fc16/fc17, ffmpeg2dirac for fc17
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-19 01:15 UTC by Steve
Modified: 2013-01-19 11:06 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-19 09:23:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
spec files, and patches to existing SRPMS (5.01 KB, application/x-bzip2)
2013-01-19 01:15 UTC, Steve
no flags Details

Description Steve 2013-01-19 01:15:17 UTC
Created attachment 682828 [details]
spec files, and patches to existing SRPMS

Kino is a non-linear DV editor for GNU/Linux that was part of the Fedora distribution until FC14.  It mostly just needed to be upgraded to the API of newer versions of ffmpeg.  The changes were minor.

ffmpeg2dirac is one of kino's dependencies, which is why I included it here instead of making a separate request.  It was part of the Fedora distribution until FC16.  It also just needed to be upgraded to the API of newer versions of ffmpeg.  The changes were REALLY minor.

kino also had an odd dependency on a kernel header; I changed it to a dependency that added libv4l-devel as a build dependency.

Install the source RPM of kino from FC14, and the source RPM of ffmpeg2dirac from FC16, then unpack the attached archive to your rpmbuild directory.  That will overwrite the spec files, and add two patches to the SOURCES directory.  You can then build ffmpeg2dirac for FC16 and kino for FC16 and FC17.

Please consider bringing kino back!  Most of the time, I vastly prefer its simplicity over kdenlive.

Comment 1 Dan Horák 2013-01-19 09:23:39 UTC
Kino was never part of Fedora, it was part of RPM Fusion because its non-free dependencies are also there.

Comment 2 Dan Horák 2013-01-19 11:06:45 UTC
And more note - Kino fails to build on F-18, so it's still a no-go. It doesn't make a lot of sense to package Kino when there is no committed person that will fix compatibility issues brought by newer ffmpeg in the future.


Note You need to log in before you can comment on or make changes to this bug.