Bug#894158: libogg: diff for NMU version 1.3.4-0.1
On 2020-12-27 00:04, Simon McVittie wrote: > On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote: > > Looking at the licenses, both RFC included in the tarball are definitely > > non-free > > According to the replies to #894158, d/copyright contains permission to > distribute those RFCs under DFSG licenses, if I'm reading correctly. I > would prefer it if this was documented by Lintian overrides, but the > maintainer doesn't seem to want to re-upload this package for any reason > that is not a significant (important? RC?) bug. Thanks, I have just noticed that preparing the NMU, looks like our mails crossed. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
On 2020-12-27 00:45, Aurelien Jarno wrote: > clone 894158 -1 > retitle -1 libogg contains RFC released under a non-free license > severity -1 serious > thanks > > On 2018-03-27 11:09, Simon McVittie wrote: > > If the RFCs are false-positives and they are actually Free Software, > > please add Lintian overrides to document this for future contributors. If > > they're non-free, then that's considered a release-critical bug (I can't > > say I'm entirely convinced that applying the DFSG equally to documentation > > is proportionate, but there have been GRs that say it's project consensus > > that we do). > > On 2020-02-29 15:22, Aurelien Jarno wrote: > > control: tags 894158 - pending > > control: tags 894207 - pending > > > > On 2020-02-05 21:46, Adrian Bunk wrote: > > > Control: tags 894158 + patch > > > Control: tags 894158 + pending > > > Control: tags 894207 + pending > > > > > > Dear maintainer, > > > > > > I've prepared an NMU for libogg (versioned as 1.3.4-0.1) and uploaded > > > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > > > > > > The package has been rejected: > > > > | libogg source: lintian output: 'license-problem-non-free-RFC > > doc/rfc3533.txt', automatically rejected package. > > | libogg source: If you have a good reason, you may override this lintian > > > > Removing the pending tags accordingly. > > Looking at the licenses, both RFC included in the tarball are definitely > non-free: > > * doc/rfc3533.txt: > > | Full Copyright Statement > | > |Copyright (C) The Internet Society (2003). All Rights Reserved. > | > |This document and translations of it may be copied and furnished to > |others, and derivative works that comment on or otherwise explain it > |or assist in its implementation may be prepared, copied, published > |and distributed, in whole or in part, without restriction of any > |kind, provided that the above copyright notice and this paragraph are > |included on all such copies and derivative works. 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. > | > |The limited permissions granted above are perpetual and will not be > |revoked by the Internet Society or its successors or assigns. > | > |This document and the information contained herein is provided on an > |"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING > |TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING > |BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION > |HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF > |MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. > > * doc/rfc5334.txt: > > |Copyright (C) The IETF Trust (2008). > | > |This document is subject to the rights, licenses and restrictions > |contained in BCP 78, and except as set forth therein, the authors > |retain all their rights. > | > |This document and the information contained herein are provided on an > |"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS > |OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND > |THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS > |OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF > |THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED > |WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. > > I am therefore cloning that bug, and I am preparing an NMU based on > latest Adrian's upload. Preparing the NMU, I realised that exceptions have been granted for these two RFCs in debian/copyright. Sorry for not noticing about that earlier. I am therefore closing the bug I have just opened. I am still preparing an NMU based on latest Adrian's upload, this time added lintian overrides so that the package do not get rejected by dak. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote: > Looking at the licenses, both RFC included in the tarball are definitely > non-free According to the replies to #894158, d/copyright contains permission to distribute those RFCs under DFSG licenses, if I'm reading correctly. I would prefer it if this was documented by Lintian overrides, but the maintainer doesn't seem to want to re-upload this package for any reason that is not a significant (important? RC?) bug. smcv
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
clone 894158 -1 retitle -1 libogg contains RFC released under a non-free license severity -1 serious thanks On 2018-03-27 11:09, Simon McVittie wrote: > If the RFCs are false-positives and they are actually Free Software, > please add Lintian overrides to document this for future contributors. If > they're non-free, then that's considered a release-critical bug (I can't > say I'm entirely convinced that applying the DFSG equally to documentation > is proportionate, but there have been GRs that say it's project consensus > that we do). On 2020-02-29 15:22, Aurelien Jarno wrote: > control: tags 894158 - pending > control: tags 894207 - pending > > On 2020-02-05 21:46, Adrian Bunk wrote: > > Control: tags 894158 + patch > > Control: tags 894158 + pending > > Control: tags 894207 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for libogg (versioned as 1.3.4-0.1) and uploaded > > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > > > The package has been rejected: > > | libogg source: lintian output: 'license-problem-non-free-RFC > doc/rfc3533.txt', automatically rejected package. > | libogg source: If you have a good reason, you may override this lintian > > Removing the pending tags accordingly. Looking at the licenses, both RFC included in the tarball are definitely non-free: * doc/rfc3533.txt: | Full Copyright Statement | |Copyright (C) The Internet Society (2003). All Rights Reserved. | |This document and translations of it may be copied and furnished to |others, and derivative works that comment on or otherwise explain it |or assist in its implementation may be prepared, copied, published |and distributed, in whole or in part, without restriction of any |kind, provided that the above copyright notice and this paragraph are |included on all such copies and derivative works. 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. | |The limited permissions granted above are perpetual and will not be |revoked by the Internet Society or its successors or assigns. | |This document and the information contained herein is provided on an |"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. * doc/rfc5334.txt: |Copyright (C) The IETF Trust (2008). | |This document is subject to the rights, licenses and restrictions |contained in BCP 78, and except as set forth therein, the authors |retain all their rights. | |This document and the information contained herein are provided on an |"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. I am therefore cloning that bug, and I am preparing an NMU based on latest Adrian's upload. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
On Mon, 13 Apr 2020 11:10:59 +0200 Petter Reinholdtsen wrote: > I notice the git repo is no longer available after git.debian.org > went away. Ron, do you plan to migrate the git repo to salsa? Looks like Ron migrated the repo to https://salsa.debian.org/ron/libogg -- Michael R. Crusoe signature.asc Description: OpenPGP digital signature
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
As 1.3.4 solve the risc-v problem, I really welcome a new version. Ron, any plan to do a new upload, possibly without the RFC text blocking the NMU? I notice the git repo is no longer available after git.debian.org went away. Ron, do you plan to migrate the git repo to salsa? -- Happy hacking Petter Reinholdtsen
Bug#894158: libogg: diff for NMU version 1.3.4-0.1
control: tags 894158 - pending control: tags 894207 - pending On 2020-02-05 21:46, Adrian Bunk wrote: > Control: tags 894158 + patch > Control: tags 894158 + pending > Control: tags 894207 + pending > > Dear maintainer, > > I've prepared an NMU for libogg (versioned as 1.3.4-0.1) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. > The package has been rejected: | libogg source: lintian output: 'license-problem-non-free-RFC doc/rfc3533.txt', automatically rejected package. | libogg source: If you have a good reason, you may override this lintian Removing the pending tags accordingly. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
