Debian Bug report logs - #936604
getmail: Python2 removal in sid/bullseye

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: maintonly@bugs.debian.org

Subject: getmail: Python2 removal in sid/bullseye

Date: Fri, 30 Aug 2019 07:18:42 +0000

Package: src:getmail
Version: 5.13-1
Severity: normal
Tags: sid bullseye
User: debian-python@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-python@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 <bug number of blocking py2removal bug> + src:getmail

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-python@lists.debian.org mailing list.

Message #10 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: Matthias Klose <doko@debian.org>, 936604-maintonly@bugs.debian.org

Cc: maintonly@bugs.debian.org

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Sat, 31 Aug 2019 18:23:35 +0900

Hi,

On Fri, Aug 30, 2019 at 07:18:42AM +0000, Matthias Klose wrote:
> Package: src:getmail
> Version: 5.13-1
> Severity: normal
> Tags: sid bullseye
> User: debian-python@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".

This package has an active upstream who feels strong about supporting
Python 2.5 etc. and has no intention to move to 3.0 (or 2.7).

We even proposed patch for 2.7 migration which was not accepted. He
insisted python 2 will be around.

> - If the package has still many users (popcon >= 300), or is needed to

getmail4: (v 4 series) popcon=2236 oldstable
getmail:  (v 5 series) popcon=890  stable, testing

Anyway, popcon >>> 300

>   build another package which cannot be removed, document that by
>   adding the "py2keep" user tag (not replacing the py2remove tag),
>   using the debian-python@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.

OK, this is what we do for now.
 
> 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-python@lists.debian.org mailing list.

Osamu

Message #20 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: 936604@bugs.debian.org, debian-python@lists.debian.org

Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Subject: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 00:37:27 +0900

Hi,

It seems I need to discuss here before adding followings.

| Package: src:getmail
| Version: 5.13-1
| Severity: normal
| Tags: sid bullseye
| User: debian-python@lists.debian.org
| Usertags: py2keep

Upstream is active and prides to keep python 2.5 compatibility code in
it ... (Not just 2.7).  I (Osamu Aoki <osamu@debian.org>) and dkg even
made some effort to support both 2 and 3 but the idea was rejected by
upstream in 2018.  (Then we both lost motivation since upstream will not
include such code in near future)
  https://marc.info/?l=getmail&m=151542515929707&w=2

The upstream is somehow convinced that python2 will be there for some
time (Year ~2020 and later).
  https://marc.info/?l=getmail&m=151542154628352&w=2
| > Python2 will be EOL after 2020.
| [...]
| > But, if getmail stays as python2 code, many distros have no choice but
| > to drop getmail sometime after 2020.
| 
| Uh, no, they won't.  Python 2 may stop *development*, but it doesn't magically
| stop working in 2020.  I fully expect distros will keep shipping Python 2 for
| years after that, and undoubtedly there will still be lots of Python 2 code
| in the world running in 2030 and later.

The related binary packages are available in 2 binary names (depending on release)
 getmail4 (version=4,5) popcon installed ~2000
 getmail  (version=3,5) popcon installed ~1000

https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1

I think this qualifies for "py2keep".

The next upload of new upstream 5.14 should update dependency etc to
python2 instead of bare python.

If Debian and Fedora demonstrate its python3 removal, I am sure the
upstream may change his thought.  If you have some progress indicator,
that can be used to convince getmail upstream.  I or dkg need a solid
fact to restart conversation with the upstream.

Regards,

Osamu

Message #23 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Mattia Rizzolo <mattia@debian.org>

To: Osamu Aoki <osamu@debian.org>

Cc: 936604@bugs.debian.org, debian-python@lists.debian.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Subject: Re: getmail: Python2 removal in sid/bullseye

Date: Tue, 12 Nov 2019 16:57:17 +0100

[Message part 1 (text/plain, inline)]

On Wed, Nov 13, 2019 at 12:37:27AM +0900, Osamu Aoki wrote:
> Upstream is active and prides to keep python 2.5 compatibility code in
> it ... (Not just 2.7).  I (Osamu Aoki <osamu@debian.org>) and dkg even
> made some effort to support both 2 and 3 but the idea was rejected by
> upstream in 2018.  (Then we both lost motivation since upstream will not
> include such code in near future)
>   https://marc.info/?l=getmail&m=151542515929707&w=2
> 
> The upstream is somehow convinced that python2 will be there for some
> time (Year ~2020 and later).
>   https://marc.info/?l=getmail&m=151542154628352&w=2

uh. meh.

I haven't looked at the code, but if you made the effort, how improbable
would it be for you to just keep the patches for py3 support yourself in
the packaging for the time being?

-- 
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 (application/pgp-signature, inline)]

Message #28 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Ondrej Novy <novy@ondrej.org>

To: Osamu Aoki <osamu@debian.org>

Cc: 936604@bugs.debian.org, debian-python <debian-python@lists.debian.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Subject: Re: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 09:27:08 +0100

[Message part 1 (text/plain, inline)]

Hi,

út 12. 11. 2019 v 16:37 odesílatel Osamu Aoki <osamu@debian.org> napsal:

> Upstream is active and prides to keep python 2.5 compatibility code in
> it ... (Not just 2.7).  I (Osamu Aoki <osamu@debian.org>) and dkg even
> made some effort to support both 2 and 3 but the idea was rejected by
> upstream in 2018.


that's odd :/


> I think this qualifies for "py2keep".
>

i don't think so. Imho is better to support Py3 in Debian with our patches.

If Debian and Fedora demonstrate its python3 removal, I am sure the
> upstream may change his thought.  If you have some progress indicator,
> that can be used to convince getmail upstream.  I or dkg need a solid
> fact to restart conversation with the upstream.
>

yes, we have! :)

http://sandrotosi.me/debian/py2removal/py2removal_progress.png

Almost half of work is done in ~ 3 months.

-- 
Best regards
 Ondřej Nový

[Message part 2 (text/html, inline)]

Message #33 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Thomas Goirand <zigo@debian.org>

To: 936604@bugs.debian.org, debian-python@lists.debian.org

Subject: Re: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 15:06:54 +0100

On 11/12/19 4:37 PM, Osamu Aoki wrote:
> The related binary packages are available in 2 binary names (depending on release)
>  getmail4 (version=4,5) popcon installed ~2000
>  getmail  (version=3,5) popcon installed ~1000
> 
> https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
> 
> I think this qualifies for "py2keep".

IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
which is still available in Debian (and with 4 times the number of
installed package in popcon...). So I see no reason to keep getmail
then. Maybe tell this to upstream, and they may think another time.

Cheers,

Thomas Goirand (zigo)

Message #38 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: Mattia Rizzolo <mattia@debian.org>, 936604@bugs.debian.org

Cc: debian-python@lists.debian.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 23:15:32 +0900

Hi,

On Tue, Nov 12, 2019 at 04:57:17PM +0100, Mattia Rizzolo wrote:
> On Wed, Nov 13, 2019 at 12:37:27AM +0900, Osamu Aoki wrote:
> > Upstream is active and prides to keep python 2.5 compatibility code in
> > it ... (Not just 2.7).  I (Osamu Aoki <osamu@debian.org>) and dkg even
> > made some effort to support both 2 and 3 but the idea was rejected by
> > upstream in 2018.  (Then we both lost motivation since upstream will not
> > include such code in near future)
> >   https://marc.info/?l=getmail&m=151542515929707&w=2
> >
> > The upstream is somehow convinced that python2 will be there for some
> > time (Year ~2020 and later).
> >   https://marc.info/?l=getmail&m=151542154628352&w=2
>
> uh. meh.
>
> I haven't looked at the code, but if you made the effort, how improbable
> would it be for you to just keep the patches for py3 support yourself in
> the packaging for the time being?

Neither of us got to compete patches to be accepted by the upstream or
fully functioning code for all versions upstream wanted to support, if I
recall correctly.

Besides, patches applied were extensive.  Considering security
implication, not accepted by upstream was the killer.  The upstream
updates this package when security concerns are raised.

Anyway, if Debian compiles a transition statistics of python3 migration,
we can point upstream to it.

Do we have stat of number of packages:
 A) Packages using python3
 B) Packages using python2 but python3 version is also available.
 C) Packages using python2 but python3 version is not available and
    it is required by standard package building
 D) Packages using python2 but python3 version is not available and
    it is not required by standard package building,
    but it has high popcon over 1000.

If "C" portion is getting less than 1% and "D" portion is getting 1% of
"A" portion, I guess upstream may change mind.

If we know how Fedora has done, that may help convince upstream.

Regards,

Osamu

Message #43 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: Ondrej Novy <novy@ondrej.org>, 936604@bugs.debian.org

Cc: debian-python <debian-python@lists.debian.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 23:22:58 +0900

Hi,

On Wed, Nov 13, 2019 at 09:27:08AM +0100, Ondrej Novy wrote:
> Hi,
>
> út 12. 11. 2019 v 16:37 odesílatel Osamu Aoki <osamu@debian.org> napsal:
>
>     Upstream is active and prides to keep python 2.5 compatibility code in
>     it ... (Not just 2.7).  I (Osamu Aoki <osamu@debian.org>) and dkg even
>     made some effort to support both 2 and 3 but the idea was rejected by
>     upstream in 2018.
>
>
> that's odd :/
>
>
>     I think this qualifies for "py2keep".
>
>
> i don't think so. Imho is better to support Py3 in Debian with our patches.

dkj: Do you?  (Not me)

>     If Debian and Fedora demonstrate its python3 removal, I am sure the
>     upstream may change his thought.  If you have some progress indicator,
>     that can be used to convince getmail upstream.  I or dkg need a solid
>     fact to restart conversation with the upstream.
>
>
> yes, we have! :)
>
> http://sandrotosi.me/debian/py2removal/py2removal_progress.png
>
> Almost half of work is done in ~ 3 months.

This is interesting.  I will inform upstream about this progress.

But how much od current ~1800 packages fall into high popcon and build
dependency category.   Are these all high pop conpackages?

Osamu

Message #48 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Iustin Pop <iustin@debian.org>

To: debian-python@lists.debian.org, 936604@bugs.debian.org

Subject: Re: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 15:31:04 +0100

On 2019-11-13 15:06:54, Thomas Goirand wrote:
> On 11/12/19 4:37 PM, Osamu Aoki wrote:
> > The related binary packages are available in 2 binary names (depending on release)
> >  getmail4 (version=4,5) popcon installed ~2000
> >  getmail  (version=3,5) popcon installed ~1000
> > 
> > https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
> > 
> > I think this qualifies for "py2keep".
> 
> IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
> which is still available in Debian (and with 4 times the number of
> installed package in popcon...). So I see no reason to keep getmail
> then. Maybe tell this to upstream, and they may think another time.

Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK)
the only tool that works for gmail with ASPs disabled (i.e. with OAUTH).

Heck, I'd be very willing to maintain Py3 patches myself, because I need
this tool.

regards,
iustin

Message #53 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: getmail@lists.pyropus.ca

Cc: 936604@bugs.debian.org, debian-python <debian-python@lists.debian.org>, dkg@fifthhorseman.net

Subject: FYI: Python 3 migration of distributuion

Date: Thu, 14 Nov 2019 00:21:07 +0900

Hi,

This is just FYI on situation.

Currently, getmail is a candidate for removal from the upcoming Debian
release if it is not updated to support python 3 by someone (not
necessary by upstream).

Here is the background ....

Debian and Ubuntu are pushing to remove python2 in next 2020 release.
  https://wiki.debian.org/Python/2Removal
  https://lists.ubuntu.com/archives/ubuntu-devel/2019-November/040842.html

You can see its progress for Debian at:
  http://sandrotosi.me/debian/py2removal/py2removal_progress.png
They converted packages to support python3 for almost the half of the
problematic python2 packages in 3 months.  With this pace, they think
they can remove python2.

Ubuntu also has list:
  https://people.canonical.com/~ubuntu-archive/transitions/html/python2-rm.html

Some migration activities were implemented by Debian maintainers
patching the upstream package without upstream help.  So something like
that may happen on getmail if some other Debian developers take actions.
(I, for one, will not do this considering getmail being a security
sensitive mail application and needs upstream support of python3 code.)

Please also note Fedora seems to be doing the similar:
  https://pagure.io/releng/issue/8221
  https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal

Please don't expect some major distros to be supporting python2 after 2020.

If you convert python 2 code for 2.7 style, then we can support both
python 2 and 3.  If some code needs to be made compatible with pre=2.7
version, may be making that section of code conditional to python
version may accommodate it without causing python 3 compatibility
problem.

If you update package to support python 3, I will upload it to Debian.

Regards,

Osamu

Message #58 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: Iustin Pop <iustin@debian.org>, 936604@bugs.debian.org

Cc: debian-python@lists.debian.org

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Thu, 14 Nov 2019 00:24:15 +0900

On Wed, Nov 13, 2019 at 03:31:04PM +0100, Iustin Pop wrote:
> On 2019-11-13 15:06:54, Thomas Goirand wrote:
> > On 11/12/19 4:37 PM, Osamu Aoki wrote:
> > > The related binary packages are available in 2 binary names (depending on release)
> > >  getmail4 (version=4,5) popcon installed ~2000
> > >  getmail  (version=3,5) popcon installed ~1000
> > >
> > > https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
> > >
> > > I think this qualifies for "py2keep".
> >
> > IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
> > which is still available in Debian (and with 4 times the number of
> > installed package in popcon...). So I see no reason to keep getmail
> > then. Maybe tell this to upstream, and they may think another time.
>
> Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK)
> the only tool that works for gmail with ASPs disabled (i.e. with OAUTH).
>
> Heck, I'd be very willing to maintain Py3 patches myself, because I need
> this tool.

Please take over packaging from me then.  You are welcome.

Osamu

Message #63 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Thomas Goirand <zigo@debian.org>

To: debian-python@lists.debian.org, 936604@bugs.debian.org

Subject: Re: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 17:37:15 +0100

On 11/13/19 3:31 PM, Iustin Pop wrote:
> On 2019-11-13 15:06:54, Thomas Goirand wrote:
>> On 11/12/19 4:37 PM, Osamu Aoki wrote:
>>> The related binary packages are available in 2 binary names (depending on release)
>>>  getmail4 (version=4,5) popcon installed ~2000
>>>  getmail  (version=3,5) popcon installed ~1000
>>>
>>> https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
>>>
>>> I think this qualifies for "py2keep".
>>
>> IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
>> which is still available in Debian (and with 4 times the number of
>> installed package in popcon...). So I see no reason to keep getmail
>> then. Maybe tell this to upstream, and they may think another time.
> 
> Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK)
> the only tool that works for gmail with ASPs disabled (i.e. with OAUTH).

Oh ! Thanks for the insight. I didn't know.

> Heck, I'd be very willing to maintain Py3 patches myself, because I need
> this tool.

Then there's no issue anymore? :)

Thomas

Message #68 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Iustin Pop <iustin@debian.org>

To: 936604@bugs.debian.org, debian-python@lists.debian.org

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Wed, 13 Nov 2019 23:55:03 +0100

On 2019-11-14 00:24:15, Osamu Aoki wrote:
> On Wed, Nov 13, 2019 at 03:31:04PM +0100, Iustin Pop wrote:
> > On 2019-11-13 15:06:54, Thomas Goirand wrote:
> > > On 11/12/19 4:37 PM, Osamu Aoki wrote:
> > > > The related binary packages are available in 2 binary names (depending on release)
> > > >  getmail4 (version=4,5) popcon installed ~2000
> > > >  getmail  (version=3,5) popcon installed ~1000
> > > >
> > > > https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
> > > >
> > > > I think this qualifies for "py2keep".
> > >
> > > IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
> > > which is still available in Debian (and with 4 times the number of
> > > installed package in popcon...). So I see no reason to keep getmail
> > > then. Maybe tell this to upstream, and they may think another time.
> >
> > Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK)
> > the only tool that works for gmail with ASPs disabled (i.e. with OAUTH).
> >
> > Heck, I'd be very willing to maintain Py3 patches myself, because I need
> > this tool.
> 
> Please take over packaging from me then.  You are welcome.

I would gladly help with co-maintenance, but taking over packaging would
be my least preferred option.

Thanksfully, it seems the upstream is willing to move to Python 3, so I
think situation is pretty good, actually.

thank you!

Message #73 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: getmail@lists.pyropus.ca

Cc: Iustin Pop <iustin@debian.org>, 936604@bugs.debian.org, debian-python <debian-python@lists.debian.org>

Subject: Re: FYI: Python 3 migration of distributuion

Date: Sun, 17 Nov 2019 14:28:44 +0900

Hi,

On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> Osamu Aoki <osamu@debian.org> wrote:
> >
> > Currently, getmail is a candidate for removal from the upcoming Debian
> > release if it is not updated to support python 3 by someone (not
> > necessary by upstream).
>
> Thanks for the update, Osamu.  I have actually been playing with a prototype
> refactoring of getmail to not just support but require a recent Python 3.x
> version.  Such a project would give me the opportunity to remove a lot of
> historical cruft and backwards-compatibility code that getmail has accumulated
> over 20+ years.

That's great.  (I thought you rejected idea to move to 3.0.)

I tried to do it around getmail 5.5 days.  (I didn't finish it)

> Unfortunately, it's difficult to find the hours to devote to this task.  I
> don't know when, or even if, I could have a beta release ready.
>
> > If you convert python 2 code for 2.7 style, then we can support both
> > python 2 and 3.
>
> I'm not very interested in doing this, as it means not using a lot of 3.x
> features, or not using them in the most Pythonic way.  My thought was that
> this project would target at least Python 3.7; anyone who didn't want to run
> 3.7 could still run "legacy" getmail under Python 2.7.

I understand.  When I tried to convert this to Python3, the first thing
I did was clean out all backward compatibility codes, too.  It is too
much work to keep them.

Also if it is Python3 only, we don't need to add things like:

from __future__ import division
 from future import standard_library

If you have a public git repository, maybe some Debian developer may
help you.  If you want, I can set up one at salsa.debian.org (or
github.com) where ever you are comfortable.

At least, if we have a place to share work in progress, we don't
duplicate efforts.


Osamu

Message #78 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: getmail@lists.pyropus.ca

Cc: Iustin Pop <iustin@debian.org>, 936604@bugs.debian.org, debian-python <debian-python@lists.debian.org>

Subject: Re: FYI: Python 3 migration of distributuion

Date: Tue, 19 Nov 2019 22:43:49 +0900

On Sun, Nov 17, 2019 at 02:28:44PM +0900, Osamu Aoki wrote:
> Hi,
>
> On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> > Osamu Aoki <osamu@debian.org> wrote:
> > >
> > > Currently, getmail is a candidate for removal from the upcoming Debian
> > > release if it is not updated to support python 3 by someone (not
> > > necessary by upstream).
> >
> > Thanks for the update, Osamu.  I have actually been playing with a prototype
> > refactoring of getmail to not just support but require a recent Python 3.x
> > version.  Such a project would give me the opportunity to remove a lot of
> > historical cruft and backwards-compatibility code that getmail has accumulated
> > over 20+ years.
>
> That's great.  (I thought you rejected idea to move to 3.0.)
>
> I tried to do it around getmail 5.5 days.  (I didn't finish it)


FYI: I found this repo
https://gitlab.com/dkg/getmail/commits/python3
I think this is better work than my local work.

Osamu

Message #83 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

To: Iustin Pop <iustin@debian.org>, 936604@bugs.debian.org, debian-python@lists.debian.org, Osamu Aoki <osamu@debian.org>

Subject: Re: Bug#936604: getmail: Python2 removal in sid/bullseye

Date: Wed, 19 Feb 2020 11:29:43 -0500

[Message part 1 (text/plain, inline)]

On Wed 2019-11-13 15:31:04 +0100, Iustin Pop wrote:
> On 2019-11-13 15:06:54, Thomas Goirand wrote:
>> On 11/12/19 4:37 PM, Osamu Aoki wrote:
>> > The related binary packages are available in 2 binary names (depending on release)
>> >  getmail4 (version=4,5) popcon installed ~2000
>> >  getmail  (version=3,5) popcon installed ~1000
>> > 
>> > https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1
>> > 
>> > I think this qualifies for "py2keep".
>> 
>> IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail,
>> which is still available in Debian (and with 4 times the number of
>> installed package in popcon...). So I see no reason to keep getmail
>> then. Maybe tell this to upstream, and they may think another time.
>
> Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK)
> the only tool that works for gmail with ASPs disabled (i.e. with OAUTH).
>
> Heck, I'd be very willing to maintain Py3 patches myself, because I need
> this tool.

Thanks for the clarification about what you need from this tool.  I
stopped using getmail several months ago, and i'm in the process of
taking my name out of the uploaders list.  Sorry to bail on it, Osamu!
I just don't feel write being named as responsible for it when i no
longer even have python2 on many systems that i care about.

Upstream appears to indicate that getmail for python3 is likely to be a
nearly complete rewrite.

For myself, i've been using the very simple imap-dl (now in mailscripts
0.18, i'm the main author, and Sean Whitton is a very capable
maintainer).  But imap-dl doesn't have the OAUTH mechanism for gmail
built in.  If you wanted to port that mechanism into imap-dl, i'd be
happy to review it, though!

Regards,

      --dkg

[signature.asc (application/pgp-signature, inline)]

Message #96 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: Osamu Aoki <osamu@debian.org>

Cc: getmail@lists.pyropus.ca, Iustin Pop <iustin@debian.org>, 936604@bugs.debian.org, debian-python <debian-python@lists.debian.org>

Subject: Re: FYI: Python 3 migration of distributuion

Date: Wed, 21 Oct 2020 22:41:42 +0200

On Tue, Nov 19, 2019 at 10:43:49PM +0900, Osamu Aoki wrote:
> On Sun, Nov 17, 2019 at 02:28:44PM +0900, Osamu Aoki wrote:
> > Hi,
> >
> > On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> > > Osamu Aoki <osamu@debian.org> wrote:
> > > >
> > > > Currently, getmail is a candidate for removal from the upcoming Debian
> > > > release if it is not updated to support python 3 by someone (not
> > > > necessary by upstream).
> > >
> > > Thanks for the update, Osamu.  I have actually been playing with a prototype
> > > refactoring of getmail to not just support but require a recent Python 3.x
> > > version.  Such a project would give me the opportunity to remove a lot of
> > > historical cruft and backwards-compatibility code that getmail has accumulated
> > > over 20+ years.
> >
> > That's great.  (I thought you rejected idea to move to 3.0.)
> >
> > I tried to do it around getmail 5.5 days.  (I didn't finish it)
> 
> 
> FYI: I found this repo
> https://gitlab.com/dkg/getmail/commits/python3
> I think this is better work than my local work.

Hi Osamu,
given that a Py3-compatible version is now available as src:getmail6,
let's go ahead and remove getmail?

Cheers,
        Moritz    

Message #101 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: Moritz Mühlenhoff <jmm@inutil.org>, 936604@bugs.debian.org

Cc: Iustin Pop <iustin@debian.org>, debian-python <debian-python@lists.debian.org>

Subject: Re: Bug#936604: FYI: Python 3 migration of distributuion

Date: Sat, 12 Dec 2020 15:21:06 +0900

Hi,

It's a fork with a new upstream with some issues.  (Not supported by
the old upstream)

Anyway, I switched out from getmail to other MUA.

No one seems to take over this package maintenance.

So please remove this package.  I am not going to package the new
getmail6.

Regards,

Osamu


On Wed, 2020-10-21 at 22:41 +0200, Moritz Mühlenhoff wrote:
> On Tue, Nov 19, 2019 at 10:43:49PM +0900, Osamu Aoki wrote:
> > On Sun, Nov 17, 2019 at 02:28:44PM +0900, Osamu Aoki wrote:
> > > Hi,
> > > 
> > > On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> > > > Osamu Aoki <osamu@debian.org> wrote:
> > > > > 
> > > > > Currently, getmail is a candidate for removal from the
> > > > > upcoming Debian
> > > > > release if it is not updated to support python 3 by someone
> > > > > (not
> > > > > necessary by upstream).
> > > > 
> > > > Thanks for the update, Osamu.  I have actually been playing
> > > > with a prototype
> > > > refactoring of getmail to not just support but require a recent
> > > > Python 3.x
> > > > version.  Such a project would give me the opportunity to
> > > > remove a lot of
> > > > historical cruft and backwards-compatibility code that getmail
> > > > has accumulated
> > > > over 20+ years.
> > > 
> > > That's great.  (I thought you rejected idea to move to 3.0.)
> > > 
> > > I tried to do it around getmail 5.5 days.  (I didn't finish it)
> > 
> > 
> > FYI: I found this repo
> > https://gitlab.com/dkg/getmail/commits/python3
> > I think this is better work than my local work.
> 
> Hi Osamu,
> given that a Py3-compatible version is now available as src:getmail6,
> let's go ahead and remove getmail?
> 
> Cheers,
>         Moritz    

Message #106 received at 936604@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Osamu Aoki <osamu@debian.org>

Cc: 936604@bugs.debian.org, Iustin Pop <iustin@debian.org>, debian-python <debian-python@lists.debian.org>

Subject: Re: Bug#936604: FYI: Python 3 migration of distributuion

Date: Sat, 12 Dec 2020 11:29:22 +0100

On Sat, Dec 12, 2020 at 03:21:06PM +0900, Osamu Aoki wrote:
> Hi,
> 
> It's a fork with a new upstream with some issues.  (Not supported by
> the old upstream)
> 
> Anyway, I switched out from getmail to other MUA.
> 
> No one seems to take over this package maintenance.
> 
> So please remove this package.

Ack, will file an RM bug.

> I am not going to package the new getmail6.

getmail6 _is_ packaged already :-)

https://packages.qa.debian.org/g/getmail6.html

Cheers,
        Moritz

Message #111 received at 936604-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 871228-done@bugs.debian.org,872653-done@bugs.debian.org,885110-done@bugs.debian.org,888457-done@bugs.debian.org,936604-done@bugs.debian.org,947080-done@bugs.debian.org,971075-done@bugs.debian.org,

Cc: getmail@packages.debian.org

Subject: Bug#977291: Removed package(s) from unstable

Date: Mon, 14 Dec 2020 21:39:05 +0000

Version: 5.13-1+rm

Dear submitter,

as the package getmail has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/977291

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.