pyupgrade has been packaged + request to join the team
Hello everyone, Quick introduction about myself: I maintain the Ubuntu Cinnamon Remix and highly respect Debian (it's what everything is built off of). Norbert Preining recently stepped down as Cinnamon maintainer for KDE, and now we are sort of in a limbo state with me and Fabio Fantoni. However, neither of us are able to pass the NM process, primarily due to GPG keys/lack of contributions/work to Debian. Although I had a higher chance, and was able to maintain it longer, we are behind on the latest version, and I pretty much seemed to have no interest in the BTS. My previous RFS's was a handful of Nemo extensions, which happened to be at the time Bullseye freeze depression struck, and they were all expired. Now I'm trying to package things to rack up some contributions to Debian (and Ubuntu in that vein) by packaging more things. Anyways, personal story aside, so everyone knows where I'm coming from (because you won't find me on contributors.debian.org), the point of this is to announce I've packaged pyupgrade, a "tool to automatically upgrade syntax for newer versions". I was told at the DebConf BoF on etherpad to request to join the team, and then I can RFS, so here are my questions. 1. Can I be the maintainer for pyupgrade and have the team as an uploader? I'm asking this because the wiki mentions rule of thumb is the team maintaining to find a 'knowledgeable person'. 2. Can I join the team and later move pyupgrade to the python-team repos? This way I can still upload my package(s, and more as I heard some help is needed for pip at the BoF), and get contributions in for my NM. 3. When I join, for the initial release: can the git repo still be my personal salsa repo and use pypi? This way I can just get it pushed, and then later it can be adjusted to pull from a GitHub tag and moved to the team. Even after I get my maintainership for Cinnamon, I still want to stay a part of the python-team because I use a lot of it and would love to help the team. So, with that being said, can I join the team, how should I carry the initial release out? Let me know when you are ready for me to open an RFS. This closes Debbug #988658<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988658>. Repo is https://salsa.debian.org/ItzSwirlz-guest/pyupgrade [https://salsa.debian.org/assets/gitlab_logo-7ae504fe4f68fdebb3c2034e36621930cd36ea87924c11ff65dbcb8ed50dca58.png]<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> Joshua Peisach / pyupgrade<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language. salsa.debian.org -Josh
Re: pyupgrade has been packaged + request to join the team
Update: I have also packaged a fork of python-patch that is better maintained to close #845482, which is visible at https://salsa.debian.org/ItzSwirlz-guest/python-patch-ng. I've decided to set the team as Maintainer and me as Uploader this time, as I figured I would still technically be a maintainer if I was part of the team. As soon as pyupgrade gets its initial release I will do the same. -Josh From: Joshua Peisach Sent: Friday, August 27, 2021 4:44 PM To: debian-python@lists.debian.org Subject: pyupgrade has been packaged + request to join the team Hello everyone, Quick introduction about myself: I maintain the Ubuntu Cinnamon Remix and highly respect Debian (it's what everything is built off of). Norbert Preining recently stepped down as Cinnamon maintainer for KDE, and now we are sort of in a limbo state with me and Fabio Fantoni. However, neither of us are able to pass the NM process, primarily due to GPG keys/lack of contributions/work to Debian. Although I had a higher chance, and was able to maintain it longer, we are behind on the latest version, and I pretty much seemed to have no interest in the BTS. My previous RFS's was a handful of Nemo extensions, which happened to be at the time Bullseye freeze depression struck, and they were all expired. Now I'm trying to package things to rack up some contributions to Debian (and Ubuntu in that vein) by packaging more things. Anyways, personal story aside, so everyone knows where I'm coming from (because you won't find me on contributors.debian.org), the point of this is to announce I've packaged pyupgrade, a "tool to automatically upgrade syntax for newer versions". I was told at the DebConf BoF on etherpad to request to join the team, and then I can RFS, so here are my questions. 1. Can I be the maintainer for pyupgrade and have the team as an uploader? I'm asking this because the wiki mentions rule of thumb is the team maintaining to find a 'knowledgeable person'. 2. Can I join the team and later move pyupgrade to the python-team repos? This way I can still upload my package(s, and more as I heard some help is needed for pip at the BoF), and get contributions in for my NM. 3. When I join, for the initial release: can the git repo still be my personal salsa repo and use pypi? This way I can just get it pushed, and then later it can be adjusted to pull from a GitHub tag and moved to the team. Even after I get my maintainership for Cinnamon, I still want to stay a part of the python-team because I use a lot of it and would love to help the team. So, with that being said, can I join the team, how should I carry the initial release out? Let me know when you are ready for me to open an RFS. This closes Debbug #988658<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988658>. Repo is https://salsa.debian.org/ItzSwirlz-guest/pyupgrade [https://salsa.debian.org/assets/gitlab_logo-7ae504fe4f68fdebb3c2034e36621930cd36ea87924c11ff65dbcb8ed50dca58.png]<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> Joshua Peisach / pyupgrade<https://salsa.debian.org/ItzSwirlz-guest/pyupgrade> A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language. salsa.debian.org -Josh
Request to join the team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! Stefano: Thanks for reviewing my email! and not just my email, all the others who have requested to join the team! I feel like it's a bit rare to find people who welcome new people rarely, but I'm probably way out of touch. My official statement: I would like to join the Debian Python Team to maintain the pyupgrade, patch-ng, and the eventually the conan Python packages. I have read and agree to the DPT policy, and I have subscribed to the mailing list (fyi). My salsa login is @ItzSwirlz-guest. It appears I'll temporarily have to bounce back pyupgrade and patch-ng's version field from 'unstable' back to UNRELEASED. This will allow the standards-version to be upgraded to 4.6.0, and have final extra double-checks. Finally, for the record my public SSH and PGP key can be found just commited to my GitHub profile page: https://github.com/ItzSwirlz/ItzSwirlz/commit/b5de4166e7d04cf48e14f1b0c39bc73e889e8b8a Cheers, - -Josh -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIm0PGGEIHBOdiZ13QcPUGJr+21oFAmFD8jkACgkQQcPUGJr+ 21qE5g//WQhcRQ2Z2TUxTPL5RbIQRqd5nAnndWbcdvTEto1SVBGMMJYBM7rGvEoN vXFEKs38L3+8xzoQ5YuTJ8r/196ef9dkmURrnGISyKYMJ9s0+Gn2KXBU3jjQSLdK mHn4xI1HHcU8flBIvMXw9PjHXHnZdXHAeacAVt8II13I5UiABEGrsMx2+kc8MqLi yCCdVQyuNv1Vn3KJRyv1g7rQ9YCUu+NFC83gJREvO1PGsYymY5rOrKjT4zADfCQ8 k2M4R1QUosO8barywOoaA/zY0rlXb0mXAILylw0Q4XgmbYhhOdSqznEWQzfvBw3f 6+NNJF9wyG5TWdD2vkuVc+GVUq4xmgvbSeTKFyiv1/bA5yT6pqUufe98Rb/gzybf g42DF4HJkSXBYdtRta0B0xr7vtxJCrkQOkAuUZs0RChUmu2juTAnZ6yE35PBKsBA rE/WCE2wOYCJX4m+0F6goQ5w7MZCh0Lxm0zKZJ5cKYjfpQ2wMyGkRY/HVGq6gT7w Bm4LhLRmYGIp3PEi1iz7LyV9FKaIG8IW5NYLAYZcRbEdvNKVo0u2mzQG75Ka7ChC Dm90s1Kjcx0wTNcQ6fwLmnPhOMgUNK9Xs/4UfuCLz5L46KMBTZnZW2Ji/h5kY7PD PYwkDMPXJsGwRjQ0GnE65B0kFg8OsMzl4LH/lgQ5fanPinhpq7k= =vhP6 ---END PGP SIGNATURE-
Re: build package
Looks like doc generation failed. You can override the doc generation, not have any of it or do other alternatives (I’m not the best person for advice) From: Nilson Silva Sent: Thursday, November 17, 2022 12:57:53 PM To: debian-python@lists.debian.org Subject: build package Hello guys! Could someone help me to find out the error of this package? https://salsa.debian.org/nilsonfsilva/librosa/-/jobs/3528766 Thanks! Nilson F. Silva
