[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Non-free RFCs in stretch

Le 4 mars 2017 10:13:21 GMT+01:00, Simon Josefsson <simon@josefsson.org> a écrit :
>Hi all,
>I have searched for non-free licensed IETF RFCs in the archive and
>the files below in the stretch suite.  Compare earlier work here [1].
>I know this is late in the release cycle, but I believe these are real
>RC bugs so it appears to me that bug reports should be filed.  I post
>this here first to confirm my understanding that this is the
>way to act.  If some policy has changed that makes this not a problem
>anymore, let me know.  I'm okay to file these bugs as stretch-ignore to
>not uphold the release, if that makes the release team happier.  I wish
>I had looked earlier, but it seems an imminent release triggers various
>old habbits.
>One interesting aspect is that almost all of the RFCs below are the
>RFC1950-RFC1952 documents.  They contain this clause:
>   Copyright (c) 1996 L. Peter Deutsch and Jean-Loup Gailly
>   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.
>This does not clearly grant the right to modify the document and
>redistribute the result.  Further, I believe the IETF Trust claim
>copyright on all RFCs, even older documents, so the content of the RFC
>itself may not be the entire story.  It might be wortwhile to reach out
>to the authors to see if they can publish the documents under a clear
>and DFSG-compatible license.  I don't have time for this though,
>volunteers welcome.
>pkg binutils ver
>  binutils-
>  binutils-
>  binutils-
>pkg binutils-avr ver 2.26.20160125+Atmel3.5.3-1
>  binutils/zlib/doc/rfc1950.txt
>  binutils/zlib/doc/rfc1951.txt
>  binutils/zlib/doc/rfc1952.txt
>pkg cargo ver 0.15.0~dev-1
>  deps/libz-sys-1.0.7/src/zlib-1.2.8/doc/rfc1950.txt
>  deps/libz-sys-1.0.7/src/zlib-1.2.8/doc/rfc1952.txt
>  deps/libz-sys-1.0.7/src/zlib-1.2.8/doc/rfc1951.txt
>pkg critcl ver 3.1.9-1
>  critcl-3.1.9/examples/zlibwrap/zlib/doc/rfc1950.txt
>  critcl-3.1.9/examples/zlibwrap/zlib/doc/rfc1951.txt
>  critcl-3.1.9/examples/zlibwrap/zlib/doc/rfc1952.txt
>pkg fossil ver 1:1.37-1
>  Fossil_2017-01-16_205854_1669115ab9/compat/zlib/doc/rfc1950.txt
>  Fossil_2017-01-16_205854_1669115ab9/compat/zlib/doc/rfc1951.txt
>  Fossil_2017-01-16_205854_1669115ab9/compat/zlib/doc/rfc1952.txt
>pkg inspircd ver 2.0.23-2
>  inspircd-2.0.23/docs/rfc/rfc1035.txt
>  inspircd-2.0.23/docs/rfc/rfc1413.txt
>  inspircd-2.0.23/docs/rfc/rfc1459.txt
>pkg povray ver 1:
>  povray-
>  povray-
>  povray-
>pkg tcl8.6 ver 8.6.6+dfsg-1
>  tcl8.6.6/compat/zlib/doc/rfc1950.txt
>  tcl8.6.6/compat/zlib/doc/rfc1951.txt
>  tcl8.6.6/compat/zlib/doc/rfc1952.txt

Could you check if lintian found this problems. If not could you fill a bug.

If yes could you fill a bug against fptmaster for adding to autoreject list ?

>[1] https://wiki.debian.org/NonFreeIETFDocuments

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Reply to: