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
Joining DPMT / PAPT
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 -- Pierre Equoy QA & Certification Engineer | Canonical www.canonical.com | www.ubuntu.com
Request for joining DPMT/PAPT
Hi, I'm a Google Summer of Code student working on debile[1][2][3] with Sylvestre Ledru. As part of my work during the summer, I will have to package several python modules and applications (at least [4] and [5]). I am clemux-guest on alioth, and I am submitting the requests to join DPMT and PAPT alioth projects right now. I have already joined debian-python@lists.d.o Regards, --- Clément [1] http://debile.debian.net/ [2] http://france.debian.net/evenements/minidebconf2014/debile-presentation.pdf [3] https://wiki.debian.org/SummerOfCode2014/StudentApplications/ClementSchreiner [4] https://github.com/paultag/ricky [5] https://github.com/paultag/loofah -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87egyu14og@mux.me
Re: Joining DPMT / PAPT
* Geoffrey Thomas , 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
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
* Jakub Wilk , 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
Re: Joining DPMT / PAPT
* Geoffrey Thomas , 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
Joining DPMT / PAPT
Hi! 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. 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 Thanks, -- 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.1305241736360.15...@dr-wily.mit.edu
