Debian Bug report logs - #936508
fdb: 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: fdb: Python2 removal in sid/bullseye

Date: Fri, 30 Aug 2019 07:16:59 +0000

Package: src:fdb
Version: 2.0.0-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:fdb

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 #22 received at 936508@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <debian@kitterman.com>

To: 936508@bugs.debian.org

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

Date: Sat, 07 Dec 2019 15:27:58 -0500

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

On Fri, 30 Aug 2019 07:16:59 +0000 Matthias Klose <doko@debian.org> wrote:
> Package: src:fdb
> Version: 2.0.0-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.
...

Technically this is blocked by #938555, but it's only a Suggests relationship, 
so I would think it's OK to go ahead to drop the python-fdb binary.  If you 
are busy and would prefer someone else handle it, please let me know and I'll 
be glad to do an NMU.

Scott K

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

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

From: Russell Stuart <russell-debian@stuart.id.au>

To: Scott Kitterman <debian@kitterman.com>, 936508@bugs.debian.org

Subject: Re: Bug#936508: fdb: Python2 removal in sid/bullseye

Date: Sun, 08 Dec 2019 09:23:50 +1000

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

On Sat, 2019-12-07 at 15:27 -0500, Scott Kitterman wrote:
> Technically this is blocked by #938555, but it's only a Suggests
> relationship, so I would think it's OK to go ahead to drop the
> python-fdb binary.  If you are busy and would prefer someone else
> handle it, please let me know and I'll be glad to do an NMU.

My view is the appropriate time to look at it is when python2 is
dropped.  Until then it's speculation as to whether it will be dropped,
and I'm not interested in doing things that may have to be undone
latter.

Please do not NMU.

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

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

From: Scott Kitterman <debian@kitterman.com>

To: 936508@bugs.debian.org

Subject: Re: Bug#936508: fdb: Python2 removal in sid/bullseye

Date: Sat, 07 Dec 2019 23:46:55 +0000

On December 7, 2019 11:23:50 PM UTC, Russell Stuart <russell-debian@stuart.id.au> wrote:
>On Sat, 2019-12-07 at 15:27 -0500, Scott Kitterman wrote:
>> Technically this is blocked by #938555, but it's only a Suggests
>> relationship, so I would think it's OK to go ahead to drop the
>> python-fdb binary.  If you are busy and would prefer someone else
>> handle it, please let me know and I'll be glad to do an NMU.
>
>My view is the appropriate time to look at it is when python2 is
>dropped.  Until then it's speculation as to whether it will be dropped,
>and I'm not interested in doing things that may have to be undone
>latter.
>
>Please do not NMU.

I won't, but I think you have it backwards.  Until changes like this are made, python2 can't be removed.  Your approach leaves us with a Catch 22.

Scott K

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

From: Russell Stuart <russell-debian@stuart.id.au>

To: Scott Kitterman <debian@kitterman.com>, 936508@bugs.debian.org

Subject: Re: Bug#936508: fdb: Python2 removal in sid/bullseye

Date: Sun, 08 Dec 2019 11:03:42 +1000

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

On Sat, 2019-12-07 at 23:46 +0000, Scott Kitterman wrote:
> I won't, but I think you have it backwards.  Until changes like this
> are made, python2 can't be removed.  Your approach leaves us with a
> Catch 22.

Thanks.

Part of the reason for my reluctance is I don't understand the haste in
removing Python2.  It will wither and die anyway in it's own time, but
why is it necessary to speed that process up?

As the fdb maintainer I agree it would be nice to have just one version
to support, but I am also a fdb user.  For a user it creates a lot of
urgent work.  I (I suspect like a lot of sysadmin's who use python as
an alternative to bash) have accumulated a lot of python2 scripts over
the decades.  When I touch one I convert it to python3, but it's a slow
process.  I can't see any good reason to speed it up, and it doesn't
help python3 is worse than python2 as a bash replacement.

Now you are forcing me to speed that process up.  If I thought I was an
outlier then c'est la vie I guess, but my gut feeling is I am not, and
there have been comments made in passing on debian-devel that back that
up.

There hasn't been much discussion so far, but when it happens I suspect
there is going to be a lot of push back.  Thus my wait and see
attitude.  In the mean time if maintaining Python2 is too much of a
burden you could always orphan it.

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

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

From: Scott Kitterman <debian@kitterman.com>

To: 936508@bugs.debian.org

Subject: Re: Bug#936508: fdb: Python2 removal in sid/bullseye

Date: Sat, 07 Dec 2019 21:13:52 -0500

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

On Saturday, December 7, 2019 8:03:42 PM EST Russell Stuart wrote:
> On Sat, 2019-12-07 at 23:46 +0000, Scott Kitterman wrote:
> > I won't, but I think you have it backwards.  Until changes like this
> > are made, python2 can't be removed.  Your approach leaves us with a
> > Catch 22.
> 
> Thanks.
> 
> Part of the reason for my reluctance is I don't understand the haste in
> removing Python2.  It will wither and die anyway in it's own time, but
> why is it necessary to speed that process up?
> 
> As the fdb maintainer I agree it would be nice to have just one version
> to support, but I am also a fdb user.  For a user it creates a lot of
> urgent work.  I (I suspect like a lot of sysadmin's who use python as
> an alternative to bash) have accumulated a lot of python2 scripts over
> the decades.  When I touch one I convert it to python3, but it's a slow
> process.  I can't see any good reason to speed it up, and it doesn't
> help python3 is worse than python2 as a bash replacement.
> 
> Now you are forcing me to speed that process up.  If I thought I was an
> outlier then c'est la vie I guess, but my gut feeling is I am not, and
> there have been comments made in passing on debian-devel that back that
> up.
> 
> There hasn't been much discussion so far, but when it happens I suspect
> there is going to be a lot of push back.  Thus my wait and see
> attitude.  In the mean time if maintaining Python2 is too much of a
> burden you could always orphan it.

Neither the Debian Python interpreter maintainer nor the members of the major 
Python related teams (DPMT and PAPT) think shipping a python interpreter 
without security support is a good idea.  That's, AIUI, the primary driver.  
So far, I think we're about 60% through the upgrading/removal of python2 
related packages.

So far, there hasn't been significant push back that I've seen.  So far, we've 
been trying to gracefully unwind the python2 stack without breaking a lot of 
things.  I think it's more likely that things would get less graceful than 
that the goal would be abandoned.  At some point python-future is going to be 
removed from Testing and you'll have to decide if you want to ship fdb in the 
next release or not.

I'll go back to just waiting and seeing how this plays out.

Scott K

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

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

From: Sandro Tosi <morph@debian.org>

To: 936508@bugs.debian.org

Subject: fdb: diff for NMU version 2.0.0-1.1

Date: Mon, 30 Dec 2019 22:59:55 -0500

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

Control: tags 936508 + patch


Dear maintainer,

I've prepared an NMU for fdb (versioned as 2.0.0-1.1). The diff
is attached to this message.

Regards.

[fdb-2.0.0-1.1-nmu.diff (text/x-diff, attachment)]

Message #56 received at 936508-close@bugs.debian.org (full text, mbox, reply):

From: Sandro Tosi <morph@debian.org>

To: 936508-close@bugs.debian.org

Subject: Bug#936508: fixed in fdb 2.0.0-1.1

Date: Tue, 31 Dec 2019 04:19:14 +0000

Source: fdb
Source-Version: 2.0.0-1.1

We believe that the bug you reported is fixed in the latest version of
fdb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936508@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <morph@debian.org> (supplier of updated fdb package)

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 30 Dec 2019 22:53:40 -0500
Source: fdb
Architecture: source
Version: 2.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Russell Stuart <russell-debian@stuart.id.au>
Changed-By: Sandro Tosi <morph@debian.org>
Closes: 936508
Changes:
 fdb (2.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936508
Checksums-Sha1:
 5e01722d701463d86fd09b864125682f869874eb 1884 fdb_2.0.0-1.1.dsc
 a654d9609a87a536c9c38fb0752dc9ba23eb2d04 4812 fdb_2.0.0-1.1.debian.tar.xz
 cee8ccb676d9d19869135b418732a37b7ea433c4 5619 fdb_2.0.0-1.1_source.buildinfo
Checksums-Sha256:
 6a4f89f70be9eb4b1426eb4070a8b51817990caf199c2e56855b47bb8f8f992c 1884 fdb_2.0.0-1.1.dsc
 c06d05319117d2f3b9e2b5b3ccedc56d7cef3fc910215e899ca2b30089c5a326 4812 fdb_2.0.0-1.1.debian.tar.xz
 3119d14557714613a89450a22595b0736655bca55ba30c79e8de4b43f1573a35 5619 fdb_2.0.0-1.1_source.buildinfo
Files:
 6d55c64b2fa2bd8e14036361f255d389 1884 python optional fdb_2.0.0-1.1.dsc
 d3ef351f5d3f625a7c6b6340b96d1a85 4812 python optional fdb_2.0.0-1.1.debian.tar.xz
 af29cdd4d3b0132e6ccacdd4aa9bbd6b 5619 python optional fdb_2.0.0-1.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4Kx7QACgkQh588mTgB
qU9KzxAArT3MgrIiNSbmXHhAkoRb+Yi3EomsP8JjNoK//e3z05I6zuCn+Bm18DdL
f3AbLCggK28bsOJZBM2OFVm9cYleyhiY3Gs1poE+EF38/9x7PTyODUEL/xl0FPVi
DSnzOEv9f4c5282J33bZwtCP53SqirsSb9rP90/RR6MmAAthBqJeBWaGO2OhEzu+
K0JnkWjNGhCO60R3tNUOqZgP/YaJZi+NF/l2K1h0ycV2bsKUeJhGbrklprH2K+m2
dLwN0ZVkAMABiN8m8nMRxq53LxfKG0NzVHv758JYoGPuw2NZfJTVXwn5FXIa7dRb
veTnB6MpRmvTdqpDbZr9WCqtKkNR4vUpXZzmbNpMkeT42PzHCR3N5Q68DBpv+3Gx
F6kC0ku3/NdBUbE12CQRfqzE/qotMey75oDKeaUQSEU3PG6mBgD58n+1KcAa1geM
hAH5kYyE+AaiHd1shsUWRjMVoeaVq96ckUUknaUz8lbDdcxqVHgblYHwDj2RDfSk
ftvf2g9Q5KlLbsUEQ9p9RpoxlxRjF2a0coU2wuZCTJaPBwZmXNFZYV7n8WvuUTuP
14nxZKfb8TifU4o/0MZQAorj+8RvPUI2DMrUBMPX59UNaREE3UpVOJeNbm4xuPhq
SM9YmqXBPokBBy+IOyQgydwqh2PbiE5S7DKi0Fic3Cu3bubbOTA=
=RINY
-----END PGP SIGNATURE-----

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

From: Bastian Germann <bastiangermann@fishpost.de>

To: 936508@bugs.debian.org

Subject: fdb: Python2 removal in sid/bullseye

Date: Wed, 1 Jul 2020 13:37:10 +0200

What was the point of introducing the python-fdb (py2) package again? It
will never enter testing.

Message #82 received at 936508-close@bugs.debian.org (full text, mbox, reply):

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

To: 936508-close@bugs.debian.org

Subject: Bug#936508: fixed in fdb 2.0.1-2

Date: Wed, 05 Aug 2020 22:18:34 +0000

Source: fdb
Source-Version: 2.0.1-2
Done: Moritz Muehlenhoff <jmm@debian.org>

We believe that the bug you reported is fixed in the latest version of
fdb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936508@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Moritz Muehlenhoff <jmm@debian.org> (supplier of updated fdb package)

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 05 Aug 2020 23:30:22 +0200
Source: fdb
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Moritz Muehlenhoff <jmm@debian.org>
Closes: 936508
Changes:
 fdb (2.0.1-2) unstable; urgency=medium
 .
   * QA upload
   * Set maintainer to Debian QA group
   * Drop Python 2 again (was reintroduced in 2.0.1-1) (Closes: #936508)
Checksums-Sha1:
 cb378fd27124da359a9546505e8c22003997ebe9 1918 fdb_2.0.1-2.dsc
 d2926687c3af2a2e346267ff0c1fafb57bd3dcd0 4896 fdb_2.0.1-2.debian.tar.xz
 6fc954d2503100942087b7b02630b6f58c3505e9 7404 fdb_2.0.1-2_amd64.buildinfo
Checksums-Sha256:
 4824566510e8cb4740d125978c45e6b24a48d9b13a8a866f53430f306736f3c0 1918 fdb_2.0.1-2.dsc
 1f40c6678fb280c1298c4930546a1077a627061731e14bfc27f8f4f50c1a9e19 4896 fdb_2.0.1-2.debian.tar.xz
 f51c889b7fbf00d9f75ae7255f6dfb4d5761c7e0586dbe598af5a876e9246dbd 7404 fdb_2.0.1-2_amd64.buildinfo
Files:
 57f2c96af4f4cef8b5d3895057c6a5a8 1918 python optional fdb_2.0.1-2.dsc
 33e0f8ed8727ab496a350e1683c3b3e4 4896 python optional fdb_2.0.1-2.debian.tar.xz
 c53a660fa501828d1fd600958f7fdc26 7404 python optional fdb_2.0.1-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAl8rLNAACgkQEMKTtsN8
Tja+hA/8DV96cdKU36W0ZLKi4g1heEnhVvgqn/kdJeNnkWz5nAEXG+tGXZnuDwmk
ivsDRPf1rc6wYCGD7Zp2sYRDvFSmOhq2BYf46FAp+L5f2sJprBSwWw8kd9XpH/A2
OvnkZrn3sFNvrY/TP1TBRaWrjPn+sR1as0iUbhSFmovcl+plec9RbDrztGYsAqlp
uHowHncQ9jLS1+Bee8FUaRpNoc87GZesetw9O7EtsQk4DPpKIeMDIlse+xZhijJJ
o53+ZEl+ZaYAU56Wcw0RQoYrSiJ2eIwa8cRry+0b+4Ve6Vr+ahviqyB6bnVHo7WN
9slgZLYc5Z/yq83NBC++EFTyZEpk8UvAkJzsYYQ6z8Zvz04RdbGPaUmTbRMBlDgG
RRTy2mjFD9eJ6lBmi94r5Igi/xEuxgVl2AR56B+srwsLetZxgyIjfzbEhmTjV79W
hW4F8aGo5PaoNJ5OsQyg4DO+ZuqrUvgrXmp2tWzcUjgTJnsW3psnZZeOJt+Pbi+B
vQnHTtq+A8CjwQdaYBuZvQvzu8wIq9S/+BqNhUIXLHHv2ror3dao3q8Rz+577jYs
Lj955VC7JlABFyboA/o2QBeL9XhJl1rAfT+v/h1pR4DY3/EEVocHFmmTwhLLdCKo
3t2B7Wz5JfCkhgNI9Md55Xatf2yjmy+J2f1eFmCKq4EezsgitQI=
=7uc0
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.