Bug#945439: ITP: python-pyluach -- Hebrew (Jewish) calendar dates and Hebrew-Gregorian conversions
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-pyluach Version : 1.0.1 Upstream Author : Meir S. List * URL : https://github.com/simlist/pyluach/ * License : Expat Programming Lang: Python Description : Hebrew (Jewish) calendar dates and Hebrew-Gregorian conversions Pyluach is a Python package for manipulating Hebrew (Jewish) calendar dates and Hebrew-Gregorian conversions. . Features: * Conversion between Hebrew and Gregorian dates * Finding the difference between two dates * Finding a date at a given duration from the given date * Rich comparisons between dates * Finding the weekday of a given date * Finding the weekly Parsha reading of a given date I intend to maintain this as part of the DPMT as a prerequisite for a future workalendar package. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl3a6P4RHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90WozsQgAsHwIP5wnm1qWakwm1fJ3psHubfZkIRh3 TCMaBcP96AVTy30YYkOP9+OWIhrStI6sgtl1FCDSGbtpm/fU7Uxi9ZrJVZD3eIaW PONtztSaOUUTSsorS3JPE5uubRgsVzAaPCgE/VHVtWeTF0TNZ3ZU4Sa6HZoKsllk vYKG4BQ4c6xYdZq4gzUHhIBRXQq1CRsp//8JBawfpWODJDdqjF1bP85F/Q9Uc5FV C84+OFe5uFxP7b107AAQv5w2k4Leg319JqFhwf96amGaQiRagW69utcYn9jNdKtm 4yr0TPKm03Q535b95oQfq7skiHjoqhN7Vg5aF7QBnEox3xg45pZ9kw== =wMZi -END PGP SIGNATURE-
Re: RFS: opentracing-python/2.2.0-2 [ITP] -- opentracing interface for Python
Hello Thomas, I have tried to fix all the issues you have mentioned in 2.2.0-2: dget -x https://mentors.debian.net/debian/pool/main/o/opentracing-python/opentracing-python_2.2.0-2.dsc Could you please have a look and/or sponsor the package? Thanks a lot! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Join DPMT
Hello I'm packaging three python packages : python-lesscpy, prelude-correlator and prewikka. When discussing about this ITP https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941657 , Peter Wienemann proposed me to became a member of DPMT and I think this is a good idea ! My salsa login is totol-guest I have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and I accept it. Regards Thanks Thomas
Re: RFS: opentracing-python/2.2.0-2 [ITP] -- opentracing interface for Python
On 11/24/19 10:42 PM, Fabrice BAUZAC-STEHLY wrote: > Hello Thomas, > > I have tried to fix all the issues you have mentioned in 2.2.0-2: > > dget -x > https://mentors.debian.net/debian/pool/main/o/opentracing-python/opentracing-python_2.2.0-2.dsc > > Could you please have a look and/or sponsor the package? > > Thanks a lot! > > Best regards Well, remove the 2nd entry in debian/changelog: this package has never been uploaded to Debian, so you are documenting something that never happened in Debian. Cheers, Thomas Goirand (zigo)
Re: RFS: opentracing-python/2.2.0-1 [ITP] -- opentracing interface for Python
On 11/20/19 10:53 PM, Fabrice BAUZAC-STEHLY wrote: > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/o/opentracing-python/opentracing-python_2.2.0-1.dsc Hi, My review. d/changelog: No need to write "[ Fabrice BAUZAC ]". That's for when there's multiple persons in the changelog. d/compat: = Please get rid of this file, and in d/control write debhelper-compat (=12) instead (and remove debhelper there). d/control: == Not mandatory, but it'd be nice to run "wrap-and-sort -bastk" to clean-up build-depends ordering. d/copyright: There's no "Files: *" entry there, and it looks like you're listing all the files of upstream. Please don't do that. The only blocker I see is about d/copyright, the other things are more cosmetic changes that I'm suggesting. Cheers, Thomas Goirand (zigo)
Re: Bug#943785: RFS: python-pyjsparser (ITP bug #943785)
Hi Nick, On 11.11.19 20:01, Peter Wienemann wrote: * d/copyright - the only copyright dates I can see in the source are 2014-2015 Judging from the source files, you are right. Judging from the git commit history I see commits between 2015 and 2019. What is a better guideline for copyright years: copyright notices in the source or the git history? Maybe it would be best to combine both information which would yield 2014-2019. Once I know what should be used, I will update the copyright file accordingly. I asked on IRC how to handle this situation. The answer was: Use the copyright years from the copyright notices in the source. I have just pushed a commit with the corresponding change to salsa. Peter
