kivy package in trouble?
Hello, I am a user of the python3-kivy package and just noticed that kivy is no longer listed in buster [1]. Is help needed? (I am not a DD, but I am willing to test and submit packaging patches if it would help.) [1] https://packages.debian.org/search?keywords=python3-kivy signature.asc Description: OpenPGP digital signature
Request for backport of python3-kivy
Hello, would someone be willing to upload the kivy package to buster-backports? Kivy was present in jessie and stretch and will be present in bullseye, but it didn't make it into buster. It would be nice for improved continuity if, at least, it was present in buster-backports. The current salsa master (1.10.1-2) builds and runs just fine on buster. Thanks, Dean signature.asc Description: OpenPGP digital signature
Request to join the team
Hello, I would like to join the Debian python team. My immediate interest is in updating the python3-kivy package and generally keeping packages I care about up to date. My salsa username is duelafn. I have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and accept it. Thanks! Dean Serenevy (duelafn) signature.asc Description: OpenPGP digital signature
Request to join the team or Request for sponsor
Hello, would like to join the Debian python team. My immediate interest is in updating the python3-kivy package and generally keeping packages I use up to date. My salsa username is duelafn. I have read the team policy[1] and accept it. If instead I need to first build up some street-cred, I have prepared the kivy upgrade in my personal fork[2] and would like to request a sponsor to merge these changes into the team repository. Thanks! Dean Serenevy (duelafn) [1] https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst [2] https://salsa.debian.org/duelafn/kivy signature.asc Description: OpenPGP digital signature
Re: review for kivy/2.1.0-1
Hi, thanks! > * 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? [1] https://lists.debian.org/debian-legal/2005/01/msg00519.html > * Rules, lintian: are the files in kivy/tools/image-testsuite somehow > used by or called from within kivy? The readme in there talks about > generating image test suites for kivy's imageloaders. I don't know > whether this is something end users of kivy normally do; if not, > probably best to not install that directory at all rather than > appease lintian with an override and that chmod in d/rules. > > [1]https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-short-name signature.asc Description: OpenPGP digital signature
