Description of problem: According to `yum info dnf`, dnf is a fork of yum (which according to `yum info yum` is distributed under the terms o GNU GPLv2+). However, according to the output of the very same command line, dnf is distributed under the terms of GNU GPLv2+, GNU GPLv2 and GNU GPL. GNU GPLv2 and GNU GPL are not compatible licences, which means that by doing that you are violating the license of yum (GNU GPLv2+). Version-Release number of selected component (if applicable): dnf 0.3.11 yum 3.4.3 Steps to reproduce: 1. yum info dnf 2. yum info yum By the + along with the license name, it is meant that you can distribute the following source code under the terms of the such license or any *later* version of this license released by the Free Software Foundation.
(In reply to Marcel Ribeiro Dantas from comment #0) > Description of problem: > According to `yum info dnf`, dnf is a fork of yum (which according to `yum > info yum` is distributed under the terms o GNU GPLv2+). However, according > to the output of the very same command line, dnf is distributed under the > terms of GNU GPLv2+, GNU GPLv2 and GNU GPL. It means different parts (files) of DNF are distributed under one of these licenses, not that DNF as a whole is distributed under arbitrary license from the set. It is Yum that does not properly mention all of its licenses[1] I should also mention that the DNF upstream is making some effort towards removing the source files that are not GNU GPLv2+ but as all the licensing experts out there can imagine, it's not that easy and simply moving moving the functionality into different files (i.e. refactoring) is not what is going to cut it. [1] http://lists.baseurl.org/pipermail/yum-devel/2012-July/009376.html