Re: joining the PAPT
Louis-Philippe Véronneau: > On 20-05-11 17 h 02, Louis-Philippe Véronneau wrote: >> On 20-05-11 16 h 48, Utkarsh Gupta wrote: >>> Hi Hans, >>> >>> On Tue, May 12, 2020 at 2:03 AM Hans-Christoph Steiner >>> wrote: Ok, this has become a bit more urgent since someone has moved my package fdroidserver into PAPT without asking me. Now I cannot push commits to it. So either someone needs to grant me PAPT access or put my package back where it was in salsa. I'm fine with fdroidserver being in PAPT, I'm not fine with being locked out of my package. >>> >>> I am sorry this happened (though I've no idea who did it). >>> Whilst I don't have the right permissions/access to add you to PAPT >>> officially, I have given you maintainer access to fdroidserver so this >>> won't be a blocker to you. >> >> Hi, >> >> That was I, and I documented the process in bug #946105 [1]. As stated >> on the BTS, the package was already in the PAPT but wasn't respecting >> the policy, thus making team work harder. >> >> Looking at the package, it seems I forgot to push a patch to d/control >> to change the VCS. Sorry for overlooking that, I did a bunch in a row >> and must have skipped fdroidserver by mistake. >> >> I'll do that in a few minutes. >> >> Sorry if the changes to the repository path I made caused you problems. >> >> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946105 >> > > Hmm, re-reading the BTS entry, it seems I went a little fast and didn't > take in account you put the PAPT in the "Uploaders" field instead of the > "Maintainer" one. I shouldn't have touched the package. > > I guess that's why I didn't originally push a patch. Somehow > fdroidserver ended up in the list I gave to the Salsa team when I asked > them to migrate a bunch of repositories for us. > > Again, sorry for the screw up :( All's well that ends well. I've got access now and I'm happy to have the package in PAPT. I put this package as Uploaders: since I'm also upstream on fdroidserver, and we generally try to sync the release process with Debian, so new upstream releases should be handled accordingly. .hc
Re: joining the PAPT
On 20-05-11 16 h 48, Utkarsh Gupta wrote: > Hi Hans, > > On Tue, May 12, 2020 at 2:03 AM Hans-Christoph Steiner wrote: >> Ok, this has become a bit more urgent since someone has moved my package >> fdroidserver into PAPT without asking me. Now I cannot push commits to >> it. So either someone needs to grant me PAPT access or put my package >> back where it was in salsa. I'm fine with fdroidserver being in PAPT, >> I'm not fine with being locked out of my package. > > I am sorry this happened (though I've no idea who did it). > Whilst I don't have the right permissions/access to add you to PAPT > officially, I have given you maintainer access to fdroidserver so this > won't be a blocker to you. Hi, That was I, and I documented the process in bug #946105 [1]. As stated on the BTS, the package was already in the PAPT but wasn't respecting the policy, thus making team work harder. Looking at the package, it seems I forgot to push a patch to d/control to change the VCS. Sorry for overlooking that, I did a bunch in a row and must have skipped fdroidserver by mistake. I'll do that in a few minutes. Sorry if the changes to the repository path I made caused you problems. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946105 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Re: joining the PAPT
Ok, this has become a bit more urgent since someone has moved my package fdroidserver into PAPT without asking me. Now I cannot push commits to it. So either someone needs to grant me PAPT access or put my package back where it was in salsa. I'm fine with fdroidserver being in PAPT, I'm not fine with being locked out of my package. .hc Hans-Christoph Steiner: > > Hey all, > > I'm a DD and a long time member of PMPT I would like to join the PAPT. > I am packaging https://github.com/cryptax/droidlysis and I think it > fits best in PAPT. I am also willing to be a sponsor for packages I > know something about or are simple enough that I can understand them. > > I have read and accept the PAPT policy at > https://salsa.debian.org/python-team/tools/python-apps/-/blob/c0eb83b9/policy.rst > > My salsa username is eighthave, same as PMPT. > > .hc > >
Re: Joining the PAPT team
Hi, po 9. 3. 2020 v 18:19 odesílatel Berthold Gehrke napsal: > Hello dear PAPT, > > I would like to join this team to maintain (for now together with a > sposor) 'my' package asciidoc3 see https://asciidoc3.org. > welcome :) -- Best regards Ondřej Nový
Re: Joining the PAPT team
Hi Devid (2020.01.16_19:33:19_+) > My Salsa username is d.filoni-guest . Re-added. Welcome back. I'll assume you agreed to the team policy, back in the Alioth days... https://salsa.debian.org/python-team/tools/python-apps/blob/master/policy.rst SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the PAPT team
Hi Louis-Philippe (2019.06.13_18:55:19_+0200) > Ping. I haven't heard back from anyone on the list :( I also asked about > this on IRC and no one replied. Added. Welcome! Sorry, my mail is a dumpster fire. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the PAPT team
On 2019-06-01 5:03 p.m., Louis-Philippe Véronneau wrote: > Hi! > > I would like to join the PAPT team to package various python > applications I maintain upstream, such as: > > * Imap Spam Begone (isbg) [1] > * rename-flac [2] > * genfo [3] > > I'm currently am non-uploading DD, but I've started packaging stuff [4] > (currently in NEW). > > My Salsa login is: pollo > > I have read the PAPT policy [5] and agree to it. > > [1]: https://github.com/isbg/isbg > [2]: https://gitlab.com/baldurmen/rename-flac > [3]: https://gitlab.com/baldurmen/genfo > [4]: https://salsa.debian.org/debian/firmware-tomu > [5]: > https://salsa.debian.org/python-team/tools/python-apps/blob/master/policy.rst > Ping. I haven't heard back from anyone on the list :( I also asked about this on IRC and no one replied. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Re: Joining DPMT / PAPT
On Tuesday, December 08, 2015 04:54:16 PM Pierre Equoy wrote: > Hello! > > I've been working on packaging and maintaining Checkbox [1] packages. > > I would like to join the Debian Python Modules Team and the Python > Applications Packaging Team in order to maintain the Checkbox-related > packages on Debian. > > My Alioth login is pierre-equoy-guest. > > I have read and accept the policy if this team: > https://python-modules.alioth.debian.org/policy.html > > Regards, > > [1]: https://launchpad.net/checkbox Welcome to the team. Scott K
Re: Joining DPMT / PAPT
[Pierre Equoy, 2015-12-08] > I've been working on packaging and maintaining Checkbox [1] packages. > > I would like to join the Debian Python Modules Team and the Python > Applications Packaging Team in order to maintain the Checkbox-related > packages on Debian. > > My Alioth login is pierre-equoy-guest. welcome :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: PGP signature
Re: Joining the PAPT with roundup
On Jan 27, 2014, at 10:50 PM, Kai Storbeck wrote: Should I replay my git commits on subversion, or can I create a huge commit that will show the work done up to now? Would someone be interested in the small intermediate commits? They sound boring to me :) IMHO it's up to you, but Subversion being what it is, it's probably fine to just mass catchup in one big commit. -Barry signature.asc Description: PGP signature
Re: Joining the PAPT with roundup
On 15/01/2014 23:47, Piotr Ożarowski wrote: [Kai Storbeck, 2014-01-15] My Alioth username is kaisan-guest, and I would like to request a repository on Alioth for roundup. Welcome on board! Hi Piotr, and the rest, Thanks a lot. I've now uploaded my old version of roundup, being version 1.4.20 from wheezy. What is considered good practice for a package maintained by a non-DM/DD? Should I replay my git commits on subversion, or can I create a huge commit that will show the work done up to now? Would someone be interested in the small intermediate commits? They sound boring to me :) Cheers! Kai signature.asc Description: OpenPGP digital signature
Re: Joining the PAPT with roundup
[Kai Storbeck, 2014-01-15] My Alioth username is kaisan-guest, and I would like to request a repository on Alioth for roundup. Welcome on board! -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Re: Joining DPMT / PAPT
On Sat, 25 May 2013, Jakub Wilk wrote:
Welcome to DPMT!
Thanks!
I don't intend to sponsor this package, but here's my review:
I have a couple of DD friends I can bug to do the actual sponsored upload,
but review from folks with more knowledge of Python packaging and team
procedures is very useful, thanks.
Upstream provides documentation. It might be a good idea to build and ship
it.
Lintian says:
I: pygithub source: debian-watch-file-is-missing
Fixed, using githubredir.debian.net.
P: python-github: no-upstream-changelog
P: python3-github: no-upstream-changelog
There isn't one. I assume I shouldn't be creating one out of git shortlog
or something... although that does remind me that the upstream README.rst
wasn't getting installed, which is now fixed.
P: python-github: no-homepage-field
P: python3-github: no-homepage-field
Fixed.
I would drop the Provides fields:
http://lists.debian.org/debian-python/2011/03/msg00139.html
Oh, I see. Good to know. (That also makes moot my question of why
${python3:Provides} was not being set.)
Re override_dh_auto_install: -O0 is no-op when used together with
--no-compile. But then, I wouldn't use --no-compile, as is thwarts
possibility of spotting byte-compilation errors early.
I copied that from ScottK's packaging for python-ipaddr. I'm not sure why
it's there, but I can remove both of those since I don't think there's any
reason for them in this package.
Do tests require Internet connectivity? If no, then it would be good to run
them at build time.
Only one of them does (JSON encoding, github/tests/Issue142.py). I can
try to arrange to skip that one; the rest all pass under `unshare -n net`.
(There's some mechanism for mocking the API's responses.)
That said, I thought the eventual goal was to move tests to autopkgtest
instead of the build process? Are we sufficiently far away from that
reality that today I should still be putting this in the build process?
Typos in upstream code:
explicitely - explicitly
instanciate - instantiate
The code uses assert to validate types of method arguments. That's not what
assert is for.
I'll file issues / patches upstream about both of these, although no
promises about upstream agreeing with the latter stylistically. (These
should be converted into TypeErrors, right?)
Does pygithub validate SSL certificates?
Ugh. Good call, and I'm embarrassed not to have checked. Looks like it
uses httplib.HTTPSConnection, which doesn't. I will definitely come up
with a patch and file a pull request upstream before uploading!
Don't ignore errors from rm -rf build. -f takes care of ENOENT and
you failures certainly should not go unnoticed.
Oh, good to know. I'd always seen people ignoring errors from rm in
Makefile clean targets, but your reasoning makes sense.
--
Geoffrey Thomas
http://ldpreload.com
geo...@ldpreload.com
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/alpine.deb.2.00.1305251554530.27...@dr-wily.mit.edu
Re: Joining DPMT / PAPT
* Geoffrey Thomas geo...@ldpreload.com, 2013-05-26, 11:40: P: python-github: no-upstream-changelog P: python3-github: no-upstream-changelog There isn't one. What about doc/changes.rst? :) That said, I thought the eventual goal was to move tests to autopkgtest instead of the build process? Are we sufficiently far away from that reality that today I should still be putting this in the build process? I don't think there was a plan to abandon build-time testing. And anyway, we have currently no QA infrastructure for running DEP-8 tests. The code uses assert to validate types of method arguments. That's not what assert is for. [...] (These should be converted into TypeErrors, right?) Right. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130526190004.ga8...@jwilk.net
Re: Joining DPMT / PAPT
* Geoffrey Thomas geo...@ldpreload.com, 2013-05-24, 17:41: I'd like to join the Debian Python teams. I have two packages I'd like to package for Debian at the moment -- python-github (ITP #709682) and tratihubis (ITP not filed yet). I'm a DM and have slowly been having more time for Debian-ish stuff, so I expect that there will probably be more packages that I'd like to see in Debian as time passes. I've just submitted a request to join the Alioth DPMT group. Welcome to DPMT! I already asked on IRC, but if folks here have comments on my draft packaging for pygithub (with a python- and python3- split based on ScottK's python-ipaddr packaging), I'd definitely appreciate them: https://ldpreload.com/p/pygithub_1.14.2-1.dsc I don't intend to sponsor this package, but here's my review: Upstream provides documentation. It might be a good idea to build and ship it. Lintian says: I: pygithub source: debian-watch-file-is-missing P: python-github: no-upstream-changelog P: python-github: no-homepage-field P: python3-github: no-upstream-changelog P: python3-github: no-homepage-field I would drop the Provides fields: http://lists.debian.org/debian-python/2011/03/msg00139.html Re override_dh_auto_install: -O0 is no-op when used together with --no-compile. But then, I wouldn't use --no-compile, as is thwarts possibility of spotting byte-compilation errors early. Do tests require Internet connectivity? If no, then it would be good to run them at build time. Typos in upstream code: explicitely - explicitly instanciate - instantiate The code uses assert to validate types of method arguments. That's not what assert is for. Does pygithub validate SSL certificates? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130525115652.ga1...@jwilk.net
Re: Joining DPMT / PAPT
* Jakub Wilk jw...@debian.org, 2013-05-25, 13:56: https://ldpreload.com/p/pygithub_1.14.2-1.dsc I don't intend to sponsor this package, but here's my review: One more thing I forgot: Don't ignore errors from rm -rf build. -f takes care of ENOENT and you failures certainly should not go unnoticed. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130525120936.ga2...@jwilk.net
