Bug 589868

Summary: Review Request: darktable - Utility to organize and develop raw images
Product: [Fedora] Fedora Reporter: Edouard Bourguignon <madko>
Component: Package ReviewAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: fedora-package-review, ibrahimeser, kryzhev, madko, mail, notting, pahan, philippe.moret, thibault.north
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 565666 Environment:
Last Closed: 2010-05-07 09:39:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 565666    
Bug Blocks:    

Description Edouard Bourguignon 2010-05-07 07:15:10 UTC
This is a new review request for darktable since the original demand by ibrahim eser was closed (cf bug #565666).

Description:  
darktable is a virtual lighttable and darkroom for photographers: it manages
your digital negatives in a database and lets you view them through a zoomable
lighttable. It also enables you to develop raw images and enhance them. 

Here are my specs and rpms:
http://www.linuxed.net/~madko/fedora/darktable.spec
http://www.linuxed.net/~madko/fedora/darktable-0.5-2.fc12.src.rpm

But some Errors and warnings remain:

darktable.x86_64: E: invalid-soname /usr/lib64/libdarktable.so libdarktable.so
darktable.x86_64: W: shared-lib-calls-exit /usr/lib64/libdarktable.so
exit.5
darktable.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/darktable
['/usr/lib64']
darktable.x86_64: W: non-conffile-in-etc /etc/gconf/schemas/darktable.schemas
1 packages and 0 specfiles checked; 2 errors, 2 warnings.

But not sure how to fix them. Any idea?

Comment 1 Peter Lemenkov 2010-05-07 09:39:56 UTC

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