|Reported by:||Owned by:||pulkomandy|
Hi GrafX2 folks, I'm the package maintainer for GrafX2 in Fedora. When I went to do the update to 2.7, I noticed that you had an added 3rd party dependency on https://github.com/redcode/6502/. This code is GPLv3 or later.
The problem is that the GrafX2 code is GPLv2 only (not GPLv2 or later), and you cannot mix code that is GPLv2 only and GPLv3. That combination results in a mix of licenses that cannot be complied with simultaneously.
Note that this was not an issue before, because recoil (your other main 3rd party dependency) is GPLv2 or later (thus, compatible).
Technically, you also have some CeCILL v2 code in the mix as well (libraw2crtc.*), but since CeCILL v2 clause 5.3.4 says you can use it under the terms of any specific version of the GPL, it can adjust to be either GPLv2 or GPLv3 as needed.
Until the license compatibility issue is resolved, Fedora cannot update to the latest version.
There are a few ways you can resolve this licensing incompatibility:
- Relicense all of the GPLv2-only code files in GrafX2 to GPLv2 or later. The effective result of this is that you combine GrafX2 (GPLv2+) with recoil (GPLv2+) and 6502 (GPLv3) and the binary is effectively GPLv3. Since this is the case, you might consider instead ...
- Relicense all of the GPLv2-only code files in GrafX2 to GPLv3 (or GPLv3 or later if you want to try to future proof compatibility with a hypothetical GPLv4).
- Remove the GPLv3 code (6502), then the license compatibility issue goes away.
- Ask the 6052 upstream to relicense their code to either GPLv2 (or GPLv2 or later). I do not recommend this option, as it implies they are responsible for your license problem... but if they did this, your license compatibility issue would go away. :)
If any of this is unclear, please let me know. I have been doing FOSS licensing work for a very long time and I am happy to explain anything in more detail.