Bug 2031963

Summary: Darktable CC-BY-NC-3.0 content license is not acceptable for Fedora
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanza>
Component: darktableAssignee: Edouard Bourguignon <madko>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 35CC: asn, germano.massullo, klember, madko, oliver, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-15 14:34:42 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:
Bug Depends On:    
Bug Blocks: 182235    

Description Michael Catanzaro 2021-12-13 19:36:00 UTC 
Darktable's appstream metadata indicates it contains CC-BY-NC-3.0 content, which is banned from Fedora because it contains a commercial use restriction. See https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Bad_Licenses_3 for reference. We need to either:

 * Identify which content uses this license and remove it from our package, or
 * Remove the darktable package altogether

I'm cautiously hopeful that it's just a mistake, because I don't know which content actually uses this license, but maybe not. See also: https://github.com/darktable-org/darktable/issues/9674
Comment 1 Michael Catanzaro 2021-12-14 16:38:32 UTC 
Apparently the only problematic content is promo.svg: https://github.com/darktable-org/darktable/issues/10002#issuecomment-919335546
Comment 2 Andreas Schneider 2021-12-15 11:26:25 UTC 
This has been addressed by https://github.com/darktable-org/darktable/pull/10632
Comment 3 Michael Catanzaro 2021-12-15 14:34:42 UTC 
(In reply to Andreas Schneider from comment #2)
> This has been addressed by
> https://github.com/darktable-org/darktable/pull/10632

Yay! Closing this as it seems to have been a simple mistake, not something worth worrying about downstream now that it has been fixed by upstream.