Bug 1199414 - using %license COPYRIGHT instead of %doc is reported as an issue
Summary: using %license COPYRIGHT instead of %doc is reported as an issue
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-review
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislav Ochotnicky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 08:31 UTC by Tomáš Hozza
Modified: 2015-04-15 13:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-15 13:52:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
spec (4.94 KB, text/plain)
2015-03-06 08:31 UTC, Tomáš Hozza
no flags Details

Description Tomáš Hozza 2015-03-06 08:31:06 UTC
Created attachment 998716 [details]
spec

Description of problem:
I run fedora review on attached spec file. The COPYRIGHT is included in -license sub-package and the %license macro is used instead of %doc. If any of the final RPMs is installed, it pulls the -license subpackage, so license is always installed. fedora-review reports that the COPYRIGHT is missing and that the %doc macro should be used.

Based on https://fedoraproject.org/wiki/Packaging:LicensingGuidelines %license macro should be used.

Version-Release number of selected component (if applicable):
fedora-review-0.5.2-2.fc21.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
The review.txt contains:

Issues:
=======
- If (and only if) the source package includes the text of the license(s) in
  its own file, then that file, containing the text of the license(s) for the
  package is included in %doc.
  Note: Cannot find COPYRIGHT in rpm(s)
  See:
  http://fedoraproject.org/wiki/Packaging/LicensingGuidelines#License_Text


Expected results:
The COPYRIGHT with %license macro should be correctly detected.

Additional info:
I may be wrong on interpreting the fedora-review reported issue


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