Re: Accepted dh-python 4.20190722 (source) into unstable
Thanks. That dropped almost 1,900 packages off the tracker. Scott K On July 22, 2019 4:07:43 PM UTC, "Piotr Ożarowski" wrote: >Format: 1.8 >Date: Mon, 22 Jul 2019 17:40:36 +0200 >Source: dh-python >Architecture: source >Version: 4.20190722 >Distribution: unstable >Urgency: medium >Maintainer: Piotr Ożarowski >Changed-By: Piotr Ożarowski >Changes: > dh-python (4.20190722) unstable; urgency=medium > . > * Build-depend on python3-docutils to build manpages >(reintroduces circular dependencies problem, but makes Python 2.X >removal > a bit easier) > * Use debhelper compat level 12 > * Standards-Version is 4.4.0 now (no changes needed) >Checksums-Sha1: > ac8c505347bccfeb18a52bed2b1926593acea40a 1885 dh-python_4.20190722.dsc >95f040568004a87927182f1321d43df1bac1375c 100596 >dh-python_4.20190722.tar.xz >9bce29a7a85880a834a1a8cef864eded9ac1d603 6186 >dh-python_4.20190722_amd64.buildinfo >Checksums-Sha256: >f8644cdaef4d4e783eaef1eb08344349e5f8bcd0d68307d5c727f6e205bab4b1 1885 >dh-python_4.20190722.dsc >29f317d0084614964d451dc93115661e580323bb7ad963bcb9b2d1900137dfca 100596 >dh-python_4.20190722.tar.xz >5942e087fa50eefab88b9c814314fdf979bf3983f740cd8da252b2bd960ea5b4 6186 >dh-python_4.20190722_amd64.buildinfo >Files: >cc08e81e0fdeafadd114611ad4e6feec 1885 python optional >dh-python_4.20190722.dsc >cf5b4aedd9a2dc3e9459611cad27e228 100596 python optional >dh-python_4.20190722.tar.xz >b125e100aeeb90b8fa11ad3387347c92 6186 python optional >dh-python_4.20190722_amd64.buildinfo
Bug#932761: RM: python-fs-browser,python-fs-plugin-django,python-fs-plugin-s3,python-fs-plugin-sftp,python-fs-plugin-tahoe-lafs,python-fs-plugin-webdav -- NBS; cruft (upstream separated the source)
Package: ftp.debian.org Severity: normal Hi, please remove the following packages: python-fs-browser | 0.5.4-1 | unstable | all python-fs-plugin-django | 0.5.4-1 | unstable | all python-fs-plugin-s3 | 0.5.4-1 | unstable | all python-fs-plugin-sftp | 0.5.4-1 | unstable | all python-fs-plugin-tahoe-lafs | 0.5.4-1 | unstable | all python-fs-plugin-webdav | 0.5.4-1 | unstable | all Upstream removed the above packages from the main project since python-fs 2.0.0: * ~-s3 [1] is separated into another upstream project * ~-sftp [2], ~-django [3], ~-webdav [4] are maintained by different upstreams * others are probably gone Since there's no dependencies to the above packages in Debian, I would like to remove these pacakges for now. We can reupload these packages if needed. Thanks, Yao Wei [1]: https://pypi.org/project/fs-s3fs/ [2]: https://pypi.org/project/fs.sshfs/ [3]: https://pypi.org/project/django-pyfs/ [4]: https://pypi.org/project/fs.webdavfs/ signature.asc Description: PGP signature
Re: Python BoF and Python 2 removing
Hi, po 22. 7. 2019 v 14:23 odesílatel eamanu15 . napsal: > I am debian contributor (not DM or DD) and I am helping on > py2 removing. > thanks for help. How is the process for us? We just push to salsas and send a email > for maintainer (ML?) or we upload the package to mentors? > process is same as any other sponsoring inside DPMT. Push it to Salsa and add sponsoring request to topic of IRC channel. -- Best regards Ondřej Nový
Re: Python BoF and Python 2 removing
El lun., 22 de jul. de 2019 a la(s) 14:26, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > po 22. 7. 2019 v 14:23 odesílatel eamanu15 . > napsal: > >> I am debian contributor (not DM or DD) and I am helping on >> py2 removing. >> > > thanks for help. > > How is the process for us? We just push to salsas and send a email >> for maintainer (ML?) or we upload the package to mentors? >> > > process is same as any other sponsoring inside DPMT. Push it to Salsa and > add sponsoring request to topic of IRC channel. > Great, I will write to IRC right now :-) > > -- > Best regards > Ondřej Nový > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: Python BoF and Python 2 removing
Hello Ondrej,
I am debian contributor (not DM or DD) and I am helping on
py2 removing.
How is the process for us? We just push to salsas and send a email
for maintainer (ML?) or we upload the package to mentors?
Cheers.
El lun., 22 de jul. de 2019 a la(s) 13:48, Ondrej Novy (n...@ondrej.org)
escribió:
> Hi,
>
> during Python BoF (yesterday) we made some progress about Python 2
> removal. We agreed this:
>
> Python 2 and PyPy support can be removed (drop binary package python-
> and/or pypy-) if it's leaf module package.
>
> Feel free to team upload this drop, but check reverse
> {build-,}dependencies first!
>
> Please DON'T remove Python2 applications and non-leaf packages now.
>
> This is team decision, so please DON'T blindly NMU non-team packages.
>
> Thanks.
>
> --
> Best regards
> Ondřej Nový
>
>
--
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest
Python BoF and Python 2 removing
Hi,
during Python BoF (yesterday) we made some progress about Python 2 removal.
We agreed this:
Python 2 and PyPy support can be removed (drop binary package python-
and/or pypy-) if it's leaf module package.
Feel free to team upload this drop, but check reverse {build-,}dependencies
first!
Please DON'T remove Python2 applications and non-leaf packages now.
This is team decision, so please DON'T blindly NMU non-team packages.
Thanks.
--
Best regards
Ondřej Nový
Re: Transition tracker for rm python2 live
Hello, For a NMU for the PY2 remove I have just change the files on salsa and letting know to the maintainer or, just writte here to get help on the upload? I am debian contributor not DM or DD Cheers El dom., 21 de jul. de 2019 a la(s) 17:23, Scott Kitterman ( deb...@kitterman.com) escribió: > See https://release.debian.org/transitions/html/python2-rm.html > > The ones near the top of the stack (bottom of the page) are less likely to > have rdepends that need to be sorted before action can be taken on them. > > Scott K > > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: Use debhelper-compat instead of debian/compat
On Mon, Jul 22, 2019 at 12:53:23PM +0200, Andreas Tille wrote: > I wonder whether this is safe for backports and backports-sloppy. Yes, stretch-backports already supported it, so clearly buster-bpo and stretch-bpo-sl support it. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Re: Python2.7.13/16 build quality expectation mismatch
Ilari Jääskeläinen, le lun. 22 juil. 2019 06:01:36 +, a ecrit: > Very poor quality (unusable) builds w/o Tk and blit + w/ openssl-1.0.2. ? python is built with tk support, and recent openssl. Please be more specific in the issue you are having. Samuel
Re: Use debhelper-compat instead of debian/compat
Hi Ondrej On Thu, Jul 18, 2019 at 04:15:38PM -0300, Ondrej Novy wrote: > according to debhelper man package it's recommended to use debhelper-compat > instead of debian/compat file. > > I would like to mass-commit this change to DPMT/PAPT, example: > > https://salsa.debian.org/python-team/modules/python-geoip2/commit/bc5ce34dd9bbfe3ecb7951aead267dbdaba3376a > > Any thoughts? I wonder whether this is safe for backports and backports-sloppy. Kind regards Andreas. -- http://fam-tille.de
Python2.7.13/16 build quality expectation mismatch
Very poor quality (unusable) builds w/o Tk and blit + w/ openssl-1.0.2. Terveisin, Ilari Jääskeläinen
Re: python-intervaltree in Debian Python team maintenance
Hi Hilko, On Mon, Jul 22, 2019 at 11:54:21AM +0200, Hilko Bengen wrote: > * Andreas Tille: > > > I noticed that python-intervaltree is not maintained in Debian Python > > team. I wonder whether you might want to move this package to the > > team repository and follow the Debian Python policy (by putting the > > list as maintainer and you as Uploader). > > I don't seem to have permissions for the Salsa > https://salsa.debian.org/python-team/modules tree and thus far, I never > took the time to find out how to get them. This is the main reason why I > didn't put the package under team maintenance in the first place. Its described in DPMT policy how to become a member: https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst > Please consider my answer as permission to "hijack" the package on > behalf of the Debian Python Team. Thanks for the permission to "hijack". I did such things in the past and its way more relaxing with permission of quickly responding maintainer than with no response at all. ;-) However, I was told here at DebConf that I'm the DD with the most packages (I have not checked) and I rather would love to change this into the direction of less than more packages. Specifically since I realised that the dependency tree which is including python-intervalltree is very improbable to be ported to Python3 and I might need to remove these packages from Debian anyway. Thus my motivation to maintain that package is even lower. I'd be really happy if you apply for DPMT membership, put the Mailinglist as Maintainer and yourself as Uploader. The time is very fortunate I'd volunteer to ping DPMT maintainers here at DebConf to process your application quickly and give you permissions as quick as possible. ;-) Kind regards Andreas. -- http://fam-tille.de
Re: python-intervaltree in Debian Python team maintenance
* Andreas Tille: > I noticed that python-intervaltree is not maintained in Debian Python > team. I wonder whether you might want to move this package to the > team repository and follow the Debian Python policy (by putting the > list as maintainer and you as Uploader). Sure. I don't seem to have permissions for the Salsa https://salsa.debian.org/python-team/modules tree and thus far, I never took the time to find out how to get them. This is the main reason why I didn't put the package under team maintenance in the first place. Please consider my answer as permission to "hijack" the package on behalf of the Debian Python Team. Cheers, -Hilko
