Bug 1316552

Summary: License tag does not match actual license of code
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.2CC: ekeck, iweller, mkolaja, nhosoi, nkinder, rmeggins, sramling
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.4.0-29.el7_2 Doc Type: Bug Fix
Doc Text:
The LICENSE file contains the correct license information, which is GPLv3+. Previously, the output of the "rpm -qi 389-ds-base" command displayed an incorrect License field with an earlier license, GPLv2 with exceptions. The License field in RPM now contains the correct information.
Story Points: ---
Clone Of: 1315893 Environment:
Last Closed: 2016-03-31 22:05:01 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: 1315893    
Bug Blocks:    

Description Marcel Kolaja 2016-03-10 13:09:18 UTC
This bug has been copied from bug #1315893 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 5 Sankar Ramalingam 2016-03-11 09:56:59 UTC
Thanks Noriko! for adding bug verification steps.

Upgraded 389-ds-base packages on RHEL7.2 machine and run rpm command to check the version number of License. It shows GPLv3+. Hence, marking the bug as Verified.

[root@vm-idm-004 ~]# rpm -qi 389-ds-base | egrep "Name|Version|Release|License"
Name        : 389-ds-base
Version     : 1.3.4.0
Release     : 29.el7_2
License     : GPLv3+

Comment 7 errata-xmlrpc 2016-03-31 22:05:01 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://rhn.redhat.com/errata/RHBA-2016-0550.html