Bug#937321: presage: Python2 removal in sid/bullseye
Hi, I have uploaded the NMU for removing python sub-packages, and we can wait Matteo to see how to deal with the Python porting. Also I've updated the dh compat to 10 so that the build process can proceed with more parallelism. Regards, Aron On Sat, Jan 25, 2020 at 10:33 AM Scott Talbert wrote: > > Hi Matteo, > > I don't know if you saw, but I sent you a merge request[1] to remove the > Python subpackages in presage. They don't have any rdeps and have very > low popcon so it seems reasonable to remove them now (and they can be > added back later when Python 3 support is ready). > > Let me know if you are good with this change. > > Thanks, > Scott > > [1] https://sourceforge.net/p/presage/presage-debian/merge-requests/1/ > > On Tue, 3 Dec 2019, Matteo Vescovi wrote: > > > Hi Scott, > > > > Someone approached me and volunteered to port presage to Python 3 in late > > October, but I haven't heard back since them. > > > > Let me take a look at what kind of an effort it would be to port to python > > 3: that would be my preferred option if I can find the time to do. > > > > Else, the suggestion to remove the python pieces sound like the next best > > thing, if I can't find the time to port to python 3 now, we can then later > > reintroduce the python pieces. > > > > What are the planned timelines for the python 2 removal? > > > > Cheers, > > - Matteo > > > > > > > > > > On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert > > wrote: > > > > > > On Mon, 2 Dec 2019, Scott Talbert wrote: > > > > >> 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. > > > > > > Hi Matteo, > > > > > > Do you plan to port presage to Python 3? If not, I'll probably convert > > this > > > to an RM request as the package seems to be mostly unmaintained and is > > > blocking the removal of Python 2. > > > > Alternatively, perhaps just the Python pieces of presage can be removed, > > as those don't seem to have any rdepends? > > > > Scott > > > >
Bug#937321: presage: Python2 removal in sid/bullseye
Hi Matteo, I don't know if you saw, but I sent you a merge request[1] to remove the Python subpackages in presage. They don't have any rdeps and have very low popcon so it seems reasonable to remove them now (and they can be added back later when Python 3 support is ready). Let me know if you are good with this change. Thanks, Scott [1] https://sourceforge.net/p/presage/presage-debian/merge-requests/1/ On Tue, 3 Dec 2019, Matteo Vescovi wrote: Hi Scott, Someone approached me and volunteered to port presage to Python 3 in late October, but I haven't heard back since them. Let me take a look at what kind of an effort it would be to port to python 3: that would be my preferred option if I can find the time to do. Else, the suggestion to remove the python pieces sound like the next best thing, if I can't find the time to port to python 3 now, we can then later reintroduce the python pieces. What are the planned timelines for the python 2 removal? Cheers, - Matteo On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert wrote: On Mon, 2 Dec 2019, Scott Talbert wrote: >> 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. > > Hi Matteo, > > Do you plan to port presage to Python 3? If not, I'll probably convert this > to an RM request as the package seems to be mostly unmaintained and is > blocking the removal of Python 2. Alternatively, perhaps just the Python pieces of presage can be removed, as those don't seem to have any rdepends? Scott
Bug#937321: presage: Python2 removal in sid/bullseye
Hi Matteo, The timeline for removing python2 is "before bullseye." Because it will take a long time, the effort has started now. We are starting with leaf packages, of which presage is one, so that is why I've poked this bug. :) Thanks, Scott On Tue, 3 Dec 2019, Matteo Vescovi wrote: Hi Scott, Someone approached me and volunteered to port presage to Python 3 in late October, but I haven't heard back since them. Let me take a look at what kind of an effort it would be to port to python 3: that would be my preferred option if I can find the time to do. Else, the suggestion to remove the python pieces sound like the next best thing, if I can't find the time to port to python 3 now, we can then later reintroduce the python pieces. What are the planned timelines for the python 2 removal? Cheers, - Matteo On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert wrote: On Mon, 2 Dec 2019, Scott Talbert wrote: >> 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. > > Hi Matteo, > > Do you plan to port presage to Python 3? If not, I'll probably convert this > to an RM request as the package seems to be mostly unmaintained and is > blocking the removal of Python 2. Alternatively, perhaps just the Python pieces of presage can be removed, as those don't seem to have any rdepends? Scott
Bug#937321: presage: Python2 removal in sid/bullseye
Hi Scott, Someone approached me and volunteered to port presage to Python 3 in late October, but I haven't heard back since them. Let me take a look at what kind of an effort it would be to port to python 3: that would be my preferred option if I can find the time to do. Else, the suggestion to remove the python pieces sound like the next best thing, if I can't find the time to port to python 3 now, we can then later reintroduce the python pieces. What are the planned timelines for the python 2 removal? Cheers,- Matteo On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert wrote: On Mon, 2 Dec 2019, Scott Talbert wrote: >> 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. > > Hi Matteo, > > Do you plan to port presage to Python 3? If not, I'll probably convert this > to an RM request as the package seems to be mostly unmaintained and is > blocking the removal of Python 2. Alternatively, perhaps just the Python pieces of presage can be removed, as those don't seem to have any rdepends? Scott
Bug#937321: presage: Python2 removal in sid/bullseye
On Mon, 2 Dec 2019, Scott Talbert wrote: 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. Hi Matteo, Do you plan to port presage to Python 3? If not, I'll probably convert this to an RM request as the package seems to be mostly unmaintained and is blocking the removal of Python 2. Alternatively, perhaps just the Python pieces of presage can be removed, as those don't seem to have any rdepends? Scott
Bug#937321: presage: Python2 removal in sid/bullseye
On Fri, 30 Aug 2019, Matthias Klose wrote: 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. Hi Matteo, Do you plan to port presage to Python 3? If not, I'll probably convert this to an RM request as the package seems to be mostly unmaintained and is blocking the removal of Python 2. Thanks, Scott
