Bug 1415586

Summary: digikam is not built wit QtAV (video) support
Product: [Fedora] Fedora Reporter: Nils <bugzilla>
Component: digikamAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: alekcejk, me, rdieter, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-23 13:11:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nils 2017-01-23 07:29:46 UTC
Digikam 5.4 uses QtAV for video thumbnails and viewing. The fedora package is built without QtAV support


Version-Release number of selected component (if applicable): 5.4


See: https://kojipkgs.fedoraproject.org//packages/digikam/5.4.0/1.fc25/data/logs/x86_64/build.log

-- Could NOT find QtAV (missing:  QTAV_LIBRARIES QTAV_INCLUDE_DIRS) 
-- QtAV_FOUND       = FALSE
-- QtAV_INCLUDE_DIR = QTAV_CORE_INCLUDE_DIR-NOTFOUND QTAV_WIDGETS_INCLUDE_DIR-NOTFOUND
-- QtAV_LIBRARIES   = QTAV_CORE_LIBRARY-NOTFOUND;QTAV_WIDGETS_LIBRARY-NOTFOUND
...
--  libqtav found............................ NO  (optional)
--  digiKam will be compiled without Media Player support.
--  Please install the libqtav (version >= 1.11.0) development package.

Comment 1 Rex Dieter 2017-01-23 13:11:43 UTC
digikam upstream use of QtAV is effectively nonfree (with ffmpeg dependencies), so we cannot enable that feature in fedora.  sorry, cantfix :(

Comment 2 Nils 2017-01-24 06:42:14 UTC
Ok. Thank you for the reply.

You could write a note into the README file. This could spare someone from searching for missing deps or other settings.

Comment 3 Rex Dieter 2017-01-27 21:16:55 UTC

*** This bug has been marked as a duplicate of bug 1415498 ***