[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2020-03-27 Thread Sandro Tosi
On Fri, Mar 27, 2020 at 10:58 AM Dmitry Shachnev  wrote:
>
> On Fri, Mar 27, 2020 at 05:41:25PM +0300, Dmitry Shachnev wrote:
> > On Fri, Mar 27, 2020 at 09:55:51AM -0400, Sandro Tosi wrote:
> > > according to http://sandrotosi.me/debian/py2removal/python-sphinx_1.svg
> > > there's only one rdep left (and they've been warned already, #953949)
> > > so maybe we can start by dropping python-sphinx in unstable still
> > > maintaining 1.8.5 while we work towards uploading 2.4.3?
> > >
> > > I can take care of the dropping part, as it's generally pretty quick,
> > > but let me know what you think
> >
> > I don't mind. Feel free to do it, or I will do it myself in a couple of 
> > days.
> >
> > It should be mostly backporting 1dec718f4f501eab7cd806412a29536ad9dcfed8
> > from debian/master to debian/sid, also you can drop python2_* patches.

i've backported 1dec718f4f501eab7cd806412a29536ad9dcfed8 and uploaded
1.8.5-8 - python-sphinx was keeping a lot of python2 packages in (it
was, in fact, at the top of the list) so i'd rather drop it soon :)

> Though even if xapian-bindings is fixed, sphinx won't be able to migrate to
> testing because of pymongo.
>
> It may need backporting
> https://github.com/mongodb/mongo-python-driver/commit/da778c501761f9c7.

i'll have a look at it


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2020-03-27 Thread Dmitry Shachnev
On Fri, Mar 27, 2020 at 05:41:25PM +0300, Dmitry Shachnev wrote:
> On Fri, Mar 27, 2020 at 09:55:51AM -0400, Sandro Tosi wrote:
> > according to http://sandrotosi.me/debian/py2removal/python-sphinx_1.svg
> > there's only one rdep left (and they've been warned already, #953949)
> > so maybe we can start by dropping python-sphinx in unstable still
> > maintaining 1.8.5 while we work towards uploading 2.4.3?
> >
> > I can take care of the dropping part, as it's generally pretty quick,
> > but let me know what you think
>
> I don't mind. Feel free to do it, or I will do it myself in a couple of days.
>
> It should be mostly backporting 1dec718f4f501eab7cd806412a29536ad9dcfed8
> from debian/master to debian/sid, also you can drop python2_* patches.

Though even if xapian-bindings is fixed, sphinx won't be able to migrate to
testing because of pymongo.

It may need backporting
https://github.com/mongodb/mongo-python-driver/commit/da778c501761f9c7.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2020-03-27 Thread Dmitry Shachnev
On Fri, Mar 27, 2020 at 09:55:51AM -0400, Sandro Tosi wrote:
> according to http://sandrotosi.me/debian/py2removal/python-sphinx_1.svg
> there's only one rdep left (and they've been warned already, #953949)
> so maybe we can start by dropping python-sphinx in unstable still
> maintaining 1.8.5 while we work towards uploading 2.4.3?
>
> I can take care of the dropping part, as it's generally pretty quick,
> but let me know what you think

I don't mind. Feel free to do it, or I will do it myself in a couple of days.

It should be mostly backporting 1dec718f4f501eab7cd806412a29536ad9dcfed8
from debian/master to debian/sid, also you can drop python2_* patches.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2020-03-27 Thread Sandro Tosi
On Fri, 30 Aug 2019 07:53:21 + Matthias Klose  wrote:
> Package: src:sphinx
> Version: 1.8.5-3
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

according to http://sandrotosi.me/debian/py2removal/python-sphinx_1.svg
there's only one rdep left (and they've been warned already, #953949)
so maybe we can start by dropping python-sphinx in unstable still
maintaining 1.8.5 while we work towards uploading 2.4.3?

I can take care of the dropping part, as it's generally pretty quick,
but let me know what you think

Cheers,
Sandro

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2019-12-21 Thread Nicolas Boulenguez
Package: src:sphixn
Followup-For: Bug #938528
Control: unblock 938528 by 936624

gnat-gps embeds a python2 interpreter, but its documentation already
builds with python3.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938528: sphinx: Python2 removal in sid/bullseye

2019-08-30 Thread Matthias Klose
Package: src:sphinx
Version: 1.8.5-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:sphinx

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team