Red Hat Bugzilla – Bug 901504
libsmi included non-free files.
Last modified: 2013-02-24 03:57:25 EST
libsmi included non-free files. See debian bug number "498476" datails.
I think that this package be affected by debian bug number "498476".
Question: Is this non-free files is "content" or "firmware" ?
I think that this non-free files is not content or firmware, Its code.
1. Remove non-free files and rebuild.
2. Replace fedora free (Fedora acceptable licensed file) files.
3. Fix License tag (If this file is "content" or "firmware").
4. Remove Fedora repos.
Blocking FE-Legal, This is license problem.
If I understand it correctly:
* Fedora cannot ship any MIB files which are generated from IETF RFCs in rpm packages
* Fedora *can* ship verbatim copy of the RFCs in rpm packages and generate MIB files from them during installation
Please confirm, I am not a lawyer. If the above is true, I can imagine some solution in rpm %post scripts (it won't be a nice one though).
(In reply to comment #2)
> If I understand it correctly:
> * Fedora cannot ship any MIB files which are generated from IETF RFCs in rpm
> * Fedora *can* ship verbatim copy of the RFCs in rpm packages and generate
> MIB files from them during installation
This bug affected net-snmp, See bug 901505.
The license phrase in question (I assume, since it wasn't mentioned here specifically yet) is:
However, this document itself may not be modified in any way, such as by
removing the copyright notice or references to the Internet Society or
other Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English.
and debian considers these documentation:
One could try to argue this stuff should be consider "content" rather than documentation,
"... The one exception is that we permit content (but only content) which restricts modification as long as that is the only restriction.".
Code Components included in IETF Documents can be used for any purpose
pursuant to an open source license.
Can I use code that is included in IETF Documents in my software?
Yes. Code Components (see Question 3.2) that are embedded or included in IETF
Documents published on or after November 10, 2008, can be used, copied, distributed and modified by anyone in any manner under the open source Simplified BSD License, as described in Questions 3.2 and 3.3.
What is meant by “Code Components”?
Under the TLP, “Code Components” are any components intended to be directly
processed by a computer. This means that all forms of software code are Code
Components. The IETF Trust maintains a list of common code components at http://trustee.ietf.org/license-info/. The items on this list are automatically treated as “Code Components” for purposes of the TLP, but this list is illustrative only.
The current Code Components list explicitly calls out MIB modules:
"o Management Information Base (MIB) modules"
This is the license the IETF puts Code Components on:
It is BSD, Free and GPL-compatible. They are fine, as is, in Fedora, as long as they come with the corresponding BSD license.
That license text was missing, so I have added it to libsmi in rawhide (and F17/F18).
It is worth noting that this licensing policy was not in place when Debian initially noticed this issue, which is why they came to a different conclusion at the time. Many thanks to the IETF for making this change.
libsmi-0.4.8-11.fc17 has been submitted as an update for Fedora 17.
libsmi-0.4.8-11.fc18,net-snmp-5.7.2-5.fc18.1 has been submitted as an update for Fedora 18.
libsmi-0.4.8-11.fc18, net-snmp-5.7.2-5.fc18.1 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
libsmi-0.4.8-11.fc17, net-snmp-5.7.1-5.fc17.1 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.