Update 'tpsclient' license from LGPL v2.1 to GPL 3

[pki-bot]

This issue was migrated from Pagure Issue #1547. Originally filed by mharmsen (@mharmsen) on 2015-08-07 01:21:57:

• Assigned to nobody

---

The 'pki-tps' package contains the original 'tpsclient' which is based upon software which required the LGPL license (as it is comprised of native-based code related to the original pki-tps Apache plug-in), and a newly rewritten java-based Tomcat implementation of 'pki-tps'.

• Do we need to carry both the LGPL license for 'tpsclient' as well as the GPL license for 'pki-tps'?

To which legal responded:

It doesn't matter too much but I guess for simplification I would suggest updating
the license of tpsclient to GPL. LGPLv2.1 explicitly contemplates that such license
migration from LGPL to GPL may be done.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-08-10 23:10:07

Per CS/DS Meeting of 08/10/2015 - 10.3

Changed subject from "LGPL v2.1 to GPL2" to "LGPL v2.1 to GPL 3" since we will not change it in the 10.2.6 timeframe.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-02-27 13:58:30

Metadata Update from @mharmsen:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from edewata (@edewata) at 2018-05-17 09:59:47

Metadata Update from @edewata:

• Custom field feature adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field version adjusted to None
• Issue close_status updated to: None
• Issue set to the milestone: 10.6 (was: UNTRIAGED)

[pki-bot]

Comment from edewata (@edewata) at 2018-05-17 11:24:09

The whole license probably should be changed to GPLv3: https://www.gnu.org/licenses/rms-why-gplv3.en.html

[pki-bot]

Comment from edewata (@edewata) at 2018-05-17 12:59:52

This is needed by ticket 2978.