Bug 353421
| Summary: | license - compatibility | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | shrek-m <shrek-m> |
| Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | pnasrat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-08 13:23:55 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 353431 has been marked as a duplicate of this bug. *** Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping On rpm level, the license is just an arbitrary string. Distributions can of course mandate certain values by policy, but that's outside rpm scope. Not to mention maintaining a license-compatibility matrix and attempting to check for license compatibility - that's a job for lawyers, not rpm. For distro-level license sanity checking helper tool, you'll be far better off looking at licenses from repository metadata. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.8) Gecko/20071023 Fedora/2.0.0.8-1.fc8 Firefox/2.0.0.8 Description of problem: is it possible to check via the rpm-license-tag and the package-dependencies if there are license incompatibilities? eg. GPLv3+ vs. GPLv2only i am not sure if all %{license} are proper filed, some licenses are listed as "distributable, freeware, public domain, gpl, lgpl, ..." instead the correct version. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. repoquery -a --qf "%{name} -- %{license}\n" Actual Results: Expected Results: # rpm -q --checklicensecomp packageA packagB license conflict GPLv3+ GPLv2only Additional info: the license tag should be filed correctly in the near future. more GPLv3+ http://gplv3.fsf.org/rms_gplv3_launch_transcript