Bug#745453: [libgcrypt20] Non free RFC
On 2014-04-22 bastien ROUCARIES roucaries.bast...@gmail.com wrote: Package: libgcrypt20 Version: 1.6.1-2 Severity: serious User: debian-rele...@lists.debian.org Usertags: nonfree-doc rfc control: block 745409 by -1 control: clone -1 -2 control: reassign -2 libgcrypt11 control: found -2 1.5.3-4 Hi! This source package contains the following files from the IETF under non-free license terms: cipher/crc.c The license on RFC/I-Ds is not DFSG-free, see: * http://wiki.debian.org/NonFreeIETFDocuments * http://bugs.debian.org/199810 [...] Hello, I have taken another look at this and still have no idea whether this bug is even valid. Both rfc-editor.org and www.ietf.org still distribute RFC 1952 with the following copyright statement and license: -- Copyright (c) 1996 L. Peter Deutsch Permission is granted to copy and distribute this document for any purpose and without charge, including translations into other languages and incorporation into compilations, provided that the copyright notice and this notice are preserved, and that any substantive changes or deletions from the original are clearly marked. A pointer to the latest version of this and related documentation in HTML format can be found at the URL ftp://ftp.uu.net/graphics/png/documents/zlib/zdoc-index.html. -- The gcrypt license header says: The copyright on RFCs, and consequently the function below, are supposedly also retroactively claimed by the Internet Society (according to rfc-edi...@rfc-editor.org), with the following copyright notice: [...] I assume this refers to the mail quoted in https://wiki.debian.org/NonFreeIETFDocuments regarding RFC 1510. - However the situation with 1510 differs signigicantly from RFC 1952. The former is distributet without copyrighth statement and license-headers, while the other one has both. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745453: [libgcrypt20] Non free RFC
Two comments: 1) Looking at crc.c, I don't think the code in question is big enough to be copyrightable. The FSF usually uses a 10-line limit, and my impression is that they are intentionally conservative here. The code is a couple of lines only. 2) Code from some RFCs is available under the BSD license or for smaller snippets, under fair use, via the IETF Trust. See http://trustee.ietf.org/faq.html /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745453: [libgcrypt20] Non free RFC
On Tue, Apr 22, 2014 at 1:30 PM, Simon Josefsson si...@josefsson.org wrote: Two comments: 1) Looking at crc.c, I don't think the code in question is big enough to be copyrightable. The FSF usually uses a 10-line limit, and my impression is that they are intentionally conservative here. The code is a couple of lines only. 2) Code from some RFCs is available under the BSD license or for smaller snippets, under fair use, via the IETF Trust. See http://trustee.ietf.org/faq.html Ok this could be thus documented under your COPYING File and reflected back in debian/copyright. Bastien /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745453: [libgcrypt20] Non free RFC
You wrote: On Tue, Apr 22, 2014 at 1:30 PM, Simon Josefsson si...@josefsson.org wrote: Two comments: 1) Looking at crc.c, I don't think the code in question is big enough to be copyrightable. The FSF usually uses a 10-line limit, and my impression is that they are intentionally conservative here. The code is a couple of lines only. 2) Code from some RFCs is available under the BSD license or for smaller snippets, under fair use, via the IETF Trust. See http://trustee.ietf.org/faq.html Ok this could be thus documented under your COPYING File and reflected back in debian/copyright. Feel free to forward it upstream to Werner. I think COPYING reflect the correct licensing status of the package though, so I'm not sure what should be added there? /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745453: [libgcrypt20] Non free RFC
Package: libgcrypt20 Version: 1.6.1-2 Severity: serious User: debian-rele...@lists.debian.org Usertags: nonfree-doc rfc control: block 745409 by -1 control: clone -1 -2 control: reassign -2 libgcrypt11 control: found -2 1.5.3-4 Hi! This source package contains the following files from the IETF under non-free license terms: cipher/crc.c The license on RFC/I-Ds is not DFSG-free, see: * http://wiki.debian.org/NonFreeIETFDocuments * http://bugs.debian.org/199810 According to the squeeze/wheezy release policy, source packages must be DFSG-free, see: * http://release.debian.org/squeeze/rc_policy.txt * http://release.debian.org/wheezy/rc_policy.txt The severity is serious, because this violates the Debian policy: * http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg There are (at least) three ways to fix this problem. In order of preference: 1. Ask the author of the RFC to re-license the RFC under a free license. A template for this e-mail request can be found at http://wiki.debian.org/NonFreeIETFDocuments 2. Remove the non-free material from the source, e.g., by re-packaging the upstream archive and adding 'dfsg' to the Debian package version name. 3. Move the package to non-free. General discussions are kindly requested to take place on debian-legal or debian-devel in the thread with Subject: Non-free IETF RFC/I-Ds in source packages. Thanks, -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
