Bug 977453 - splice components should use same license
Summary: splice components should use same license
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: Splice
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 1.3
Assignee: Splice Developers
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
 
Reported: 2013-06-24 15:12 UTC by Vitaly Kuznetsov
Modified: 2013-10-01 10:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 10:59:04 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1390 0 normal SHIPPED_LIVE Release 1.3 of Subscription Asset Manager 2013-10-01 14:43:14 UTC

Description Vitaly Kuznetsov 2013-06-24 15:12:18 UTC
Description of problem:
We have different licenses for different splice components:

# for p in splice spacewalk-splice-tool ruby193-rubygem-splice_reports; do rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} %{LICENSE}\n" $p; done
splice-0.130-1.el6sam GPLv2
spacewalk-splice-tool-0.25-1.el6sam GPLv2+
ruby193-rubygem-splice_reports-0.0.5-27.el6sam GPLv2

It should be the same unless we have special reasons.

Comment 2 Bryan Kearney 2013-08-02 18:51:50 UTC
SNAP0 contains these bug fixes. Moving to ON_QA.

Comment 3 Pavlina Bartikova 2013-08-14 17:11:33 UTC
# for p in splice spacewalk-splice-tool ruby193-rubygem-splice_reports; do rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} %{LICENSE}\n" $p; done
splice-0.141-1.el6sam GPLv2+
spacewalk-splice-tool-0.39-1.el6sam GPLv2+
ruby193-rubygem-splice_reports-0.0.5-38.el6sam GPLv2+

Confirmed.

Moving bug to VERIFIED.

Comment 4 sthirugn@redhat.com 2013-08-19 18:21:34 UTC
qa_acked for Pavlina Bartikova

Comment 6 errata-xmlrpc 2013-10-01 10:59:04 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.

http://rhn.redhat.com/errata/RHEA-2013-1390.html


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