[Bug 752455] New: gcin 2.7.5 declared LGPL-2.1+ but includes GPL-2.0 licensed qt-im

https://bugzilla.novell.com/show_bug.cgi?id=752455

https://bugzilla.novell.com/show_bug.cgi?id=752455#c0


          Summary: gcin 2.7.5 declared LGPL-2.1+ but includes GPL-2.0
                   licensed qt-im
   Classification: SUSE Tools
          Product: SUSE Linux Legal Issues
          Version: unspecified
         Platform: Other
       OS/Version: Other
           Status: NEW
         Severity: Normal
         Priority: P5 - None
        Component: License Issues
       AssignedTo: swyear@gmail.com
       ReportedBy: cfarrell@suse.com
        QAContact: jw@suse.com
            Group: Legal Security Team
         Found By: ---
          Blocker: ---


The spec file for gcin 2.7.5 (as well as most of the source code files) state
that the package is LGPL-2.1+ licensed. However, a subcomponent included with
the package (qt-im) appears to be licensed under one of the older QT licenses -
a dual license choice of either the Trolltech QPL or the GPL-2.0.

If qt-im is compiled with qcin, you will need to investigate how it is used. If
it is compiled into a standalone binary with no relationship (other than e.g.
IPC or network sockets) with the LGPL-2.1+ licensed binary, then the only
problem is that the spec file should be updated to read:

License: LGPL-2.1+ and GPL-2.0

However, if the nature of the interaction is such that compiling a single
binary out of all the source code could be said to have created a derived work
(e.g. of the qt-im code), then the entire resulting binary would need to be
licensed under the GPL-2.0. This would mean the spec file should state:

License: GPL-2.0

Alternatively, if the qt-im comoponents are compiled as subpackages, then each
subpackage should carry its own license (GPL-2.0). That is currently not the
case with the qcin specfile.