Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
On Sun, Jan 17, 2021 at 11:26 PM Sudip Mukherjee wrote: > > > On Sun, 17 Jan 2021, 23:04 Mattia Rizzolo, wrote: >> >> On Sun, Jan 17, 2021 at 11:01:12PM +, Sudip Mukherjee wrote: >> > > Or is there any reason offlineimap3 should not be in bullseye? >> > >> > But offlineimap3 can only migrate after offlineimap is removed and >> > src:python-imaplib2 drops its python2 package, so I guess its better >> > to go ahead with the RM while I wait for upstream's reply. If it is >> > not removed by then, then I will upload the transitional package like >> > Mattia suggested. >> >> Then, what about this other way: >> * src:python-imaplib2 drops its python2 lib >> * ftp-master forces its removal, while keeping src:offlineimap >> ? > > > I have requested the maintainer to drop the python2 lib at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937831#27 but why do you > want to keep src:offlineimap? I am going to do a NMU to DELAYED-2 for #937831 to drop the python2 lib. -- Regards Sudip
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
On Sun, 17 Jan 2021, 23:04 Mattia Rizzolo, wrote: > On Sun, Jan 17, 2021 at 11:01:12PM +, Sudip Mukherjee wrote: > > > Or is there any reason offlineimap3 should not be in bullseye? > > > > But offlineimap3 can only migrate after offlineimap is removed and > > src:python-imaplib2 drops its python2 package, so I guess its better > > to go ahead with the RM while I wait for upstream's reply. If it is > > not removed by then, then I will upload the transitional package like > > Mattia suggested. > > Then, what about this other way: > * src:python-imaplib2 drops its python2 lib > * ftp-master forces its removal, while keeping src:offlineimap > ? > I have requested the maintainer to drop the python2 lib at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937831#27 but why do you want to keep src:offlineimap? -- Regards Sudip
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
On Sun, Jan 17, 2021 at 11:01:12PM +, Sudip Mukherjee wrote: > > Or is there any reason offlineimap3 should not be in bullseye? > > But offlineimap3 can only migrate after offlineimap is removed and > src:python-imaplib2 drops its python2 package, so I guess its better > to go ahead with the RM while I wait for upstream's reply. If it is > not removed by then, then I will upload the transitional package like > Mattia suggested. Then, what about this other way: * src:python-imaplib2 drops its python2 lib * ftp-master forces its removal, while keeping src:offlineimap ? -- 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
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
Thanks Mattia and Sean. On Sun, Jan 17, 2021 at 6:16 PM Mattia Rizzolo wrote: > > On Sun, Jan 17, 2021 at 11:06:07AM -0700, Sean Whitton wrote: > > On Sun 17 Jan 2021 at 12:12AM GMT, Sudip Mukherjee wrote: > > > On Sat, Jan 16, 2021 at 6:39 PM Moritz Muehlenhoff > > > wrote: > > >> > > >> Package: ftp.debian.org > > >> Severity: normal > > >> X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org > > >> > > >> Please remove offlineimap. It depends on Python and upstream won't port > > >> it > > >> to Python 3. There's however a fork, which has been packaged as > > >> src:offlineimap3 > > >> (and removing this obsolete package allows adding a transitional package > > >> eventually) > > > > > > That said, I encourage you to do so *now* rather than in a few months: > that way src:python-imaplib2 can drop its python2 package and > offlineimap3 can migrate to testing, with its transitional package, > therefore giving stable users an upgrade path. > > Or is there any reason offlineimap3 should not be in bullseye? There is no reason to not have offlineimap3 in Bullseye, but I am still undecided about the transitional package and waiting for the upstream confirmation at https://github.com/OfflineIMAP/offlineimap3/issues/10#issuecomment-761891100. But offlineimap3 can only migrate after offlineimap is removed and src:python-imaplib2 drops its python2 package, so I guess its better to go ahead with the RM while I wait for upstream's reply. If it is not removed by then, then I will upload the transitional package like Mattia suggested. -- Regards Sudip
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
On Sun, Jan 17, 2021 at 11:06:07AM -0700, Sean Whitton wrote: > On Sun 17 Jan 2021 at 12:12AM GMT, Sudip Mukherjee wrote: > > On Sat, Jan 16, 2021 at 6:39 PM Moritz Muehlenhoff wrote: > >> > >> Package: ftp.debian.org > >> Severity: normal > >> X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org > >> > >> Please remove offlineimap. It depends on Python and upstream won't port it > >> to Python 3. There's however a fork, which has been packaged as > >> src:offlineimap3 > >> (and removing this obsolete package allows adding a transitional package > >> eventually) > > > > I was asking in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937184#76 if it will > > be easier to update offlineimap and mark the binary package as > > transitional package instead of removing it and then going via bin-NEW > > ? If offlineimap is removed and I add it as transitional package in > > offlineimap3 then it will need an epoch in the version. > > IMO avoiding an epoch is a good reason to keep this source package > around for a few more months just to build the transitional package; if > this is what you want to do, please close this bug. That said, there is no techinical reason to not do that within the offlineimap3 source package, just use `dpkg-gencontrol -v` in d/rules to set the appropriate version string for the "offlineimap" binary package. That said, I encourage you to do so *now* rather than in a few months: that way src:python-imaplib2 can drop its python2 package and offlineimap3 can migrate to testing, with its transitional package, therefore giving stable users an upgrade path. Or is there any reason offlineimap3 should not be in bullseye? -- 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
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
Hello, On Sun 17 Jan 2021 at 12:12AM GMT, Sudip Mukherjee wrote: > Thanks Moritz. > > On Sat, Jan 16, 2021 at 6:39 PM Moritz Muehlenhoff wrote: >> >> Package: ftp.debian.org >> Severity: normal >> X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org >> >> Please remove offlineimap. It depends on Python and upstream won't port it >> to Python 3. There's however a fork, which has been packaged as >> src:offlineimap3 >> (and removing this obsolete package allows adding a transitional package >> eventually) > > I was asking in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937184#76 if it will > be easier to update offlineimap and mark the binary package as > transitional package instead of removing it and then going via bin-NEW > ? If offlineimap is removed and I add it as transitional package in > offlineimap3 then it will need an epoch in the version. IMO avoiding an epoch is a good reason to keep this source package around for a few more months just to build the transitional package; if this is what you want to do, please close this bug. -- Sean Whitton signature.asc Description: PGP signature
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
Thanks Moritz. On Sat, Jan 16, 2021 at 6:39 PM Moritz Muehlenhoff wrote: > > Package: ftp.debian.org > Severity: normal > X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org > > Please remove offlineimap. It depends on Python and upstream won't port it > to Python 3. There's however a fork, which has been packaged as > src:offlineimap3 > (and removing this obsolete package allows adding a transitional package > eventually) I was asking in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937184#76 if it will be easier to update offlineimap and mark the binary package as transitional package instead of removing it and then going via bin-NEW ? If offlineimap is removed and I add it as transitional package in offlineimap3 then it will need an epoch in the version. -- Regards Sudip
Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org Please remove offlineimap. It depends on Python and upstream won't port it to Python 3. There's however a fork, which has been packaged as src:offlineimap3 (and removing this obsolete package allows adding a transitional package eventually) Cheers, Moritz
