Re: Asking for packaging
Hi, 2018-05-09 16:02 GMT+02:00 eamanu15 : > When I make a push to the package that I maintain on salsa repo. Is > necessary upload the package to debian-mentors too? > after you push changes to salsa repo, you need sponsor for upload. Best way to find sponsor for DPMT packages is to join IRC #debian-python and ask for sponsoring there. Typically it's not needed to push it to debian-mentors, because sponsor will pull package from our git. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Decreasing fail-under parameter helps passing the test
Hi, I've checked this bug and found that root@sputnik:/build/cram-0.7# python-coverage report --fail-under=95 NameStmts Miss Cover --- cram/__init__.py3 0 100% cram/__main__.py6 6 0% cram/_cli.py 74 0 100% cram/_diff.py 89 0 100% cram/_encoding.py 67 3252% cram/_main.py 135 0 100% cram/_process.py 14 0 100% cram/_run.py 40 0 100% cram/_test.py 104 0 100% cram/_xunit.py 66 0 100% --- TOTAL 598 3894% root@sputnik:/build/cram-0.7# echo $? 2 root@sputnik:/build/cram-0.7# python-coverage report --fail-under=94 NameStmts Miss Cover --- cram/__init__.py3 0 100% cram/__main__.py6 6 0% cram/_cli.py 74 0 100% cram/_diff.py 89 0 100% cram/_encoding.py 67 3252% cram/_main.py 135 0 100% cram/_process.py 14 0 100% cram/_run.py 40 0 100% cram/_test.py 104 0 100% cram/_xunit.py 66 0 100% --- TOTAL 598 3894% root@sputnik:/build/cram-0.7# echo $? 0 so it seems that fail-under is the percentage that is permitted to fail. I'm not sure why _encoding.py and __main__.py are contributing to the failure count (obviously since some point in time). Laszlo, before I'll dive deeper into it I'd like to know what you think about maintaining this package in Debian Python Modules Team. I'd volunteer to create a Git repository on Salsa and try to fix this bug if you agree to it. Kind regards Andreas. -- http://fam-tille.de
Re: Asking for packaging
Hello! El jue., 10 de may. de 2018 a la(s) 04:36, Ondrej Novy escribió: > Hi, > > 2018-05-09 16:02 GMT+02:00 eamanu15 : > >> When I make a push to the package that I maintain on salsa repo. Is >> necessary upload the package to debian-mentors too? >> > > after you push changes to salsa repo, you need sponsor for upload. Best > way to find sponsor for DPMT packages is to join IRC #debian-python and ask > for sponsoring there. Typically it's not needed to push it to > debian-mentors, because sponsor will pull package from our git. > Ok!! Thanks very much! Best Regards! > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Mass-commit fix of lintian ancient-python-version-field
Hi, because of: - https://wiki.debian.org/Python/LibraryStyleGuide?action=diff&rev1=85&rev2=86 - https://lintian.debian.org/tags/ancient-python-version-field.html I would like to mass commit into DPMT/PAPT this: https://salsa.debian.org/python-team/modules/pytest/commit/a737368e75cb2e79f8cb61bb1615306d5f12e77a https://salsa.debian.org/python-team/modules/pytest/commit/9cb2718daa8645ab5620d719cea1937ea0eefc50 Removing Python 2 version: <= 2.7 (thus all) Removing Python 3 version: <= 3.4 (older than jessie) Any objections? Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Asking for packaging
On 05/10/2018 09:36 AM, Ondrej Novy wrote: > Typically it's not needed to push it to > debian-mentors, because sponsor will pull package from our git. That's probably the way *you* do, which is a fine way to do it. Though I, and I know a lot of other DDs, prefer to sponsor the resulting source package, rather than just being pointed at the Git. As the mentors site gives lintian results, it saves a lot of time when dealing with new comers that might not know well lintian. So I don't agree here. I'd say, just push to mentors.debian.net first, just in case your sponsor likes it, and then see if your sponsor prefers Git only. Later on, if you get into the habits of having only 1 or 2 sponsors, then maybe you'll arrange with them to use only Git. Cheers, Thomas Goirand (zigo)
Re: Asking for packaging
Hi! Ok, I could see that all agree with upload to mentors for sponsorship, I push to git. I think, that this steps, for DPMT shall be writing in the policy or in a "how to do" file to avoid confusing and to all the members do the same step. That is my humble opinion. Regards! El jue., 10 de may. de 2018 a la(s) 11:57, Thomas Goirand escribió: > On 05/10/2018 09:36 AM, Ondrej Novy wrote: > > Typically it's not needed to push it to > > debian-mentors, because sponsor will pull package from our git. > > That's probably the way *you* do, which is a fine way to do it. > > Though I, and I know a lot of other DDs, prefer to sponsor the resulting > source package, rather than just being pointed at the Git. As the > mentors site gives lintian results, it saves a lot of time when dealing > with new comers that might not know well lintian. > > So I don't agree here. I'd say, just push to mentors.debian.net first, > just in case your sponsor likes it, and then see if your sponsor prefers > Git only. Later on, if you get into the habits of having only 1 or 2 > sponsors, then maybe you'll arrange with them to use only Git. > > Cheers, > > Thomas Goirand (zigo) > > -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Re: Asking for packaging
Ah! yes! I understand Ondrej Thank you very much! El jue., 10 de may. de 2018 a la(s) 13:15, Ondrej Novy escribió: > Hi, > > 2018-05-10 16:49 GMT+02:00 eamanu15 : > >> Ok, I could see that all agree with upload to mentors for sponsorship, I >> push to git. >> > > no, I don't agree :). I'm sponsoring just from git. I don't care mentors > website at all. > > >> I think, that this steps, for DPMT shall be writing in the policy or in a >> "how to do" file to avoid confusing and to all the members do the same step. >> > > because not all agrees, it's nothing we can put inside DPMT policy. Every > sponsor have own "policy". > > It's simple: Find a sponsor (mentors ML, IRC, IRL, private message, ...) > and ask how he wants it. Different DD have different habits. > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Re: Asking for packaging
Hi, 2018-05-10 15:57 GMT+02:00 Thomas Goirand : > That's probably the way *you* do, which is a fine way to do it. > me, piotr, mapreri, ... and much guys more at IRC channel. See topic. But of course it's up to you, do it how you like it :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Asking for packaging
Hi, 2018-05-10 16:49 GMT+02:00 eamanu15 : > Ok, I could see that all agree with upload to mentors for sponsorship, I > push to git. > no, I don't agree :). I'm sponsoring just from git. I don't care mentors website at all. > I think, that this steps, for DPMT shall be writing in the policy or in a > "how to do" file to avoid confusing and to all the members do the same step. > because not all agrees, it's nothing we can put inside DPMT policy. Every sponsor have own "policy". It's simple: Find a sponsor (mentors ML, IRC, IRL, private message, ...) and ask how he wants it. Different DD have different habits. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Mass-commit fix of lintian ancient-python-version-field
On Thu, May 10, 2018 at 4:29 AM, Ondrej Novy wrote: > Removing Python 2 version: <= 2.7 (thus all) > Removing Python 3 version: <= 3.4 (older than jessie) > > Any objections? Thanks for doing that Ondřej, maybe we could delete the pycompat file when exists at the same time (in a separate commit of course) to to get rid of debian-pycompat-is-obsolete. It seems there are still 18 python modules with that file in. If not, no worries I was planning to check the packages that have this linitian tag in the next week or so, see what I can do to get rid of that. Thanks Joseph
