Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: jcfp Newsgroups: linux.debian.maint.python Subject: Re: review for kivy/2.1.0-1 Date: Sun, 01 Jan 2023 12:20:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jan 1 11:10:09 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.201 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Greylist: delayed 909 seconds by postgrey-1.36 at bendel; Sun, 01 Jan 2023 11:09:51 UTC Arc-Seal: i=1; a=rsa-sha256; t=1672570474; cv=none; d=zohomail.com; s=zohoarc; b=KwK7SUliqnP/IXUBRuTkrz5wpmWub38RZjh6PmaPhlcbcfj0lsb4N6oFT71yU2QGqyNZuNrEm8L8Ld7xoHoL5robS0kceY07AJGMYGM+MxZklB7JW+tx7bOljmW6wUaf/HQisikZBmd7U2SLe9Y3Gl/0d6msg+JTBkWqX7wKSM8= Arc-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1672570474; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=+QRSfFTcHp425WLqmulizLWZgVT55tYrfnvwzizHUI8=; b=d+5lXTUaVtbYh8iXcnYXCePFPWoZgMlk8J3OFwNfZQX/cBZ0Uwxk3Xk5ZIEuy4s5bIE4uBk8Gg9izEPZwagP1opOW5BKiJbfiBfvX2/i/4F3tQ7pQEvEfZAwugt5W7U4RFNaaLmB1eAqfvHQW3Gb4vRKGsrLkT8+dSelcTgnD8Q= Arc-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=jcf.pm; spf=pass smtp.mailfrom=linux@jcf.pm; dmarc=pass header.from= MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Mailing-List: archive/latest/20663 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/1856cf80807.ec9fdef96322.5069061886140543360@jcf.pm Approved: robomod@news.nic.it Lines: 14 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: "debian-python" X-Original-Date: Sun, 01 Jan 2023 11:54:32 +0100 X-Original-Message-ID: <1856cf80807.ec9fdef96322.5069061886140543360@jcf.pm> X-Original-References: <20221208162757.3943faea@debian.org> <56b599e4-1ce1-48d9-c0db-bf0928d9c38f@serenevy.net> <20221227192158.061b2c5d@debian.org> Xref: csiph.com linux.debian.maint.python:14791 ---- On Sun, 01 Jan 2023 07:06:20 +0100 Dean Serenevy wrote --- > > * Copyright: try using standard license shortnames [1] where > > possible: Easing appears identical to BSD-3-clause; Khronos looks > > a lot like Expat. > > You're right, the wording differed from the sample text, so I used different names, but the differences are not enough to change the license. > > I can change the Easing to use the BSD-3-clause short name, but I'm not sure what to do about the Khronos. The copyright file already has an "Expat" entry and according to Policy section 12.5. A "verbatim copy of its copyright and distribution license" must be included. An email in debian-legal [1] clarifies that really there should be no changes other than minor punctuation or whitespace variations. The standard Expat uses the word "Software" and the Khronos uses "Materials". > > If I need a verbatim copy of both licenses, don't I need to rename one of them? If I merge them, which text do I keep? I didn't do a word-for-word comparison, I usually recognise Expat because it uses some specific legalese terms. So thank you for being so precise when looking into this. If they're different enough (somewhat of an edge case here, maybe Khronos includes material that may not be universally considered "software" such as images or fonts?), you should indeed keep two entries (each with its own shortname). Maybe one Expat and the other Expat-Khronos to signal the license terms are very close but not identical? PS: I'm using an ancient laptop while waiting for a replacement part for my normal system, so it could be a few days before I can do an upload.