RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1365859 - scap-workbench rpm does not ship with LICENSE file
Summary: scap-workbench rpm does not ship with LICENSE file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-workbench
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Martin Preisler
QA Contact: Marek Haicman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-10 11:20 UTC by Marek Haicman
Modified: 2017-08-01 09:09 UTC (History)
3 users (show)

Fixed In Version: scap-workbench-1.1.4-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:09:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2296 0 normal SHIPPED_LIVE scap-workbench bug fix update 2017-08-01 12:40:10 UTC

Description Marek Haicman 2016-08-10 11:20:49 UTC
Description of problem:
Every package should install COPYING, COPYRIGHT or LICENSE file in /usr/share/doc/PACKAGE_NAME-VERSION directory. scap-workbench has correct LICENSE file in SRPM, but not in RPM.

Version-Release number of selected component (if applicable):
scap-workbench-1.1.2-1.el7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
no LICENSE file present

Expected results:
LICENSE file containing GPLv3 license installed in /usr/share/doc/scap-workbench-VERSION directory

Additional info:
Even the "About" dialog of scap-workbench mentions "You should have received a copy of the GNU General Public License along with this program."

Comment 5 Marek Haicman 2017-04-26 09:16:52 UTC
In latest version, COPYING is installed as part of package

[0 root@qeos-22 ~]# rpm -q scap-workbench
scap-workbench-1.1.4-4.el7.x86_64
[0 root@qeos-22 ~]# rpm -ql scap-workbench | grep doc
/usr/share/doc/scap-workbench-1.1.4/COPYING
/usr/share/doc/scap-workbench-1.1.4/README.md
/usr/share/doc/scap-workbench-1.1.4/user_manual.html

[0 root@qeos-22 ~]# head -2 /usr/share/doc/scap-workbench-1.1.4/COPYING
                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007

Comment 6 errata-xmlrpc 2017-08-01 09:09:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2296


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