Re: Review of Debian package pystray
hi Claudius, took a look at the pystray package up for sponsorship in the Python team. Overall it's in really good shape, still a few comments left though: * control: the long description is really short and mentions neither supported environment nor any other pystray features. * tests: + please loop over py3versions -s rather than -r; + both tests have the same test-name; + the upstream testsuite autopkgtest doesn't actually run any tests according to ci logs [1]; + for the upstream testsuite, you want to copy the test files to the $AUTOPKGTEST_TMP dir and run from there, to avoid testing the extracted sources rather than the installed package; + keeping the test commands/script in a separate file (rather than d/tests/control) tends to greatly increase readability for all but the smallest and most trivial autopkgtests. [1]https://salsa.debian.org/python-team/packages/pystray/-/jobs/3596337#L411 pgpgtW7j6XA5L.pgp Description: OpenPGP digital signature
review for weresync/1.1.5-1
hi Ileana, took a look a the weresync package you put up for sponsopship in the Python team: * weird, probably unnecessary d/source/include-binaries that lists the upstream signing key; * autopkgtest: + runs in extracted source dir, might not test installed package; + only tests with the default python version rather than all supported releases; * missing dependency on gi gtk 3.0 (gir1.2-gtk-3.0) (imported at src/weresync/interface/gui.py:28). Also, for Python team packages, please keep the target release at UNRELEASED in accordance with team policy. The sponsor will set the target release before upload. pgpyvPj11QXYR.pgp Description: OpenPGP digital signature
Re: Request to join the Python Team
Hi Sebastien (2022.03.30_20:43:25_+) > I would like to join the Debian Python Team in order to migrate > python-ncclient and python-xmltodict¹ inside the team. > And also click-option-group (new dependency of synadm²) Apologies for the very long delay. Added you to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join Debian Python Team
Hi kkremitzki (2022.10.05_17:29:50_+) > Hello, I would like to join the Debian Python Team to help with general Python > package maintenance. There is a lot of overlap with what I already work on in > the domain-specific Debian Science Team. Added, welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: join the team
Hi Nilson (2022.09.27_03:28:59_+) > I hereby request my membership as a team member! > > I already keep some packages with the team, and I'm willing to help in any > way I can! Added you, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join python-team
Hi Mohd (2022.12.03_05:37:30_+) > Just came to know about the sprint happening and I thought to use it as an > opportunity to join and contribute to the team :) Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Different behavior of package with pyproject.toml
Hi, I need some help with a package that switched to using pyproject.toml only. The package is asdf-astropy, and the problem I have that it does not package all Python files recursively: for example astropy_asdf.io files are missing (as seen in unstable now). https://tracker.debian.org/pkg/asdf-astropy https://salsa.debian.org/debian-astro-team/asdf-astropy What I do not understand is that this happens "sometimes": * when I build the package in a clean schroot with "debuild", files in subpackages are missing (but no error message in the log) * when I install git, then a debuild results in a complete package * when I cut&paste the command from the build log [1], the copy process always happens completely, independent of whether git was installed or not * when I use pbuilder, files of subpackages are never package, with our without git in the build dependencies [1] python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir .pybuild/cpython3_3.11 Since the package "sometimes" is built correctly, I think that upstream did it right; however I have no idea where the problem could be. Does anyone have an idea? Best Ole
Request to join the team
Hi, I'd like to join the Python team, mainly to maintain the python3-setuptools-golang package I've ITPed [0]. My username on Salsa is 'cavok', I read and accept the DPT Policy. Thanks, Domenico [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024839 -- rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05 signature.asc Description: PGP signature
Re: Joining the team
Hi Andrea (2022.09.24_10:09:26_+) > I'm [currently packaging][1] a C++ library which depends on [Poxy], a > documentation generator currently not packaged by Debian. I don't know much > about Python (I especially don't know anything about its ecosystem), so I > believe that joining the team is a good way to learn a bit how to package > Python programs. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the team
Hi Marcin (2022.10.20_06:56:35_+) > I want to join the team to maintain a new package, ledgerhelpers [1] > within the team. > My Salsa login is porridge Added, welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to Join
Hi Peter(2022.10.23_22:01:15_+) > Hello, > I'd like to join the maintenance team for Python. Added, welcome. And sorry about the delay. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the Debian Python Team
Hi Alper (2022.11.01_23:44:48_+) > I'm packaging "depthcharge-tools", a Python project of mine that manages > the ChromeOS bootloader to make Debian natively bootable on Chromebooks. > My sponsor already cloned it to the python-team/packages Salsa namespace > and uploaded it to NEW with the Python Team as Maintainer. I want to > join the team to keep maintaining it as part of the team. Added! Welcome to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Join python team
Hi Christopher (2022.11.02_09:21:26_+) > I'd like to join the python team and package some libraries > (e.g. https://github.com/esphome/aioesphomeapi) and their dependencies > for Debian. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join team
Hi Miah (2022.11.11_13:12:46_+) > Looking to update and maintain the nagstamon package, since I use it > daily and the packaged version crashes with icingaweb2. Added. Welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join Python team on Salsa
Hi John (2022.11.25_20:27:32_+) > I would like to join the team primarily to maintain pygopherd in Debian. Welcome! Added to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the team
Hi Stanislas (2022.09.19_19:09:40_+) > I hereby request to join the Python Team. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the team
Hi Legner, (2022.09.20_09:25:16_+) > I'm working with Claudius Heine (cmhe) and would like to join the DPT > to help maintain packages; currently I'm interested in packages related > to the TPM (tpm2-pytss) and cryptography (python-cryptography) but I > may get involved with other topics in the future. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the team
Hi Lance (2022.11.08_12:30:17_+) > I would like to formally request to join the Debian Python Team. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the team
Hi Domenico (2022.11.26_14:30:05_+) > I'd like to join the Python team, mainly to maintain the > python3-setuptools-golang package I've just ITPed. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
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: Request to join the team or Request for sponsor
Hi Dean (2022.12.04_00:49:45_+) > 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. Added, welcome to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Different behavior of package with pyproject.toml
On Saturday, December 3, 2022 11:19:06 AM EST Ole Streicher wrote: > Hi, > > I need some help with a package that switched to using pyproject.toml > only. The package is asdf-astropy, and the problem I have that it does > not package all Python files recursively: for example astropy_asdf.io > files are missing (as seen in unstable now). > > https://tracker.debian.org/pkg/asdf-astropy > https://salsa.debian.org/debian-astro-team/asdf-astropy > > What I do not understand is that this happens "sometimes": > > * when I build the package in a clean schroot with "debuild", files in > subpackages are missing (but no error message in the log) > > * when I install git, then a debuild results in a complete package > > * when I cut&paste the command from the build log [1], the copy process > always happens completely, independent of whether git was installed or > not > > * when I use pbuilder, files of subpackages are never package, with our > without git in the build dependencies > > [1] python3.11 -m build --skip-dependency-check --no-isolation --wheel > --outdir .pybuild/cpython3_3.11 > > Since the package "sometimes" is built correctly, I think that upstream > did it right; however I have no idea where the problem could be. Does > anyone have an idea? My first guess is that in some circumstances setuptools is doing the installing and in others it's the dh-python pyproject plugin (using the installer module). Looking at the build log on buildd.d.o, I can see that build is using the plugin/installer. I think it would be useful to stop the build right before the install step starts [1], manually unpack the wheel (it's a zip file) and see if it has all the files in it. If it does, then plugin/build is doing the right thing and it's an issue with either the plugin or the installer module. Since the build stage uses setuptools as part of it's build process, I thing it's most likely an installer issue. I recently found the installer module doesn't correctly handle flit data files, but I was able to work around that with appropriate .install files. Scott K [1] pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with "installer" module signature.asc Description: This is a digitally signed message part.
