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

Date: Fri, 30 Aug 2019 07:27:37 +0000

Package: src:mysql-workbench
Version: 8.0.17+dfsg-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:mysql-workbench

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

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

To: onlyjob@debian.org

Cc: 937102@bugs.debian.org

Subject: Re: mysql-workbench: Python2 removal in sid/bullseye

Date: Mon, 31 Aug 2020 20:57:56 +0200

On Fri, Aug 30, 2019 at 07:27:37AM +0000, Matthias Klose wrote:
> Package: src:mysql-workbench
> Version: 8.0.17+dfsg-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

There's radio silence on https://bugs.mysql.com/bug.php?id=98839,
let's remove?

Cheers,
        Moritz

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

From: Dmitry Smirnov <onlyjob@debian.org>

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

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Tue, 01 Sep 2020 19:11:46 +1000

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

On Tuesday, 1 September 2020 4:57:56 AM AEST Moritz Mühlenhoff wrote:
> There's radio silence on https://bugs.mysql.com/bug.php?id=98839,

They are not very transparent and their public bug tracker is somewhat 
redundant, I think... They are also slow to make transitional changes...


> let's remove?

I'd like to keep it for as long as possible please, unless you insist.

MySQL-Workbench will be very difficult to re-introduce due to slow ftp-
masters processing time for a package with that size and complexity.
It was very difficult to introduce for a first time as it required a
long and tedious review. 
I'm not looking forward to go through the process again...

-- 
Regards,
 Dmitry Smirnov.

---

The curse of man, and the cause of nearly all his woe, is his stupendous
capacity for believing the incredible.
        -- H. L. Mencken

---

The Global Political Project Imposed on the Occasion of COVID-19
    -- Thierry Meyssan, https://www.voltairenet.org/article209808.html

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

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

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

To: Dmitry Smirnov <onlyjob@debian.org>

Cc: Moritz Mühlenhoff <jmm@inutil.org>, 937102@bugs.debian.org

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Fri, 11 Sep 2020 21:09:47 +0200

On Tue, Sep 01, 2020 at 07:11:46PM +1000, Dmitry Smirnov wrote:
> On Tuesday, 1 September 2020 4:57:56 AM AEST Moritz Mühlenhoff wrote:
> > There's radio silence on https://bugs.mysql.com/bug.php?id=98839,
> 
> They are not very transparent and their public bug tracker is somewhat 
> redundant, I think... They are also slow to make transitional changes...
> 
> 
> > let's remove?
> 
> I'd like to keep it for as long as possible please, unless you insist.
> 
> MySQL-Workbench will be very difficult to re-introduce due to slow ftp-
> masters processing time for a package with that size and complexity.
> It was very difficult to introduce for a first time as it required a
> long and tedious review. 
> I'm not looking forward to go through the process again...

Fair enough, let's give upstream some more time, then.

Cheers,
        Moritz

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

From: Dmitry Smirnov <onlyjob@debian.org>

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

Cc: 937102@bugs.debian.org

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Sun, 04 Oct 2020 19:45:01 +1100

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

On Saturday, 12 September 2020 5:09:47 AM AEDT Moritz Mühlenhoff wrote:
> Fair enough, let's give upstream some more time, then.

Upstream told me that they are working on transition to Python3 and that
they expect it to be ready "by early next year (probably in the January 
release)".

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

A study on infectivity of asymptomatic SARS-CoV-2 carriers, concludes weak
transmission. "The median contact time for patients was four days and that
for family members was five days."
    -- https://pubmed.ncbi.nlm.nih.gov/32513410/

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

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

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

To: Dmitry Smirnov <onlyjob@debian.org>

Cc: Moritz Mühlenhoff <jmm@inutil.org>, 937102@bugs.debian.org

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Fri, 22 Jan 2021 20:28:09 +0100

Am Sun, Oct 04, 2020 at 07:45:01PM +1100 schrieb Dmitry Smirnov:
> On Saturday, 12 September 2020 5:09:47 AM AEDT Moritz Mühlenhoff wrote:
> > Fair enough, let's give upstream some more time, then.
> 
> Upstream told me that they are working on transition to Python3 and that
> they expect it to be ready "by early next year (probably in the January 
> release)".

Indeed, the latest 8.0.23 release is now fixed:

| * MySQL Workbench now uses Python 3 for functionality such
|   as migration, scripting shell, administrative tasks, and
|  its SQL IDE.

Cheers,
        Moritz

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

From: Dmitry Smirnov <onlyjob@debian.org>

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

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Sun, 24 Jan 2021 19:10:14 +1100

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

On Saturday, 23 January 2021 6:28:09 AM AEDT Moritz Mühlenhoff wrote:
> Indeed, the latest 8.0.23 release is now fixed:
> | * MySQL Workbench now uses Python 3 for functionality such
> |   as migration, scripting shell, administrative tasks, and
> |  its SQL IDE.

Just released, thanks for letting me know. It's been just several days
since I've checked for new release. :)

I've updated packaging for 8.0.23 but could not fix a new FTBFS problem...

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

The great enemy of the truth is very often not the lie -- deliberate,
contrived and dishonest, but the myth, persistent, persuasive, and
unrealistic. Belief in myths allows the comfort of opinion without the
discomfort of thought.
    -- John F Kennedy

---

And how long a lockdown is enough? If we open now, will lockdown recur in
autumn? Next year? Whenever authoritarianism so wishes? No dictatorship
could imagine a better precedent for absolute control.
    -- https://www.bmj.com/content/369/bmj.m1924.long
    :: BMJ 2020;369:m1924 "Should governments continue lockdown to slow the spread of covid-19?"

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

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

From: Adrian Bunk <bunk@debian.org>

To: Dmitry Smirnov <onlyjob@debian.org>, 937102@bugs.debian.org

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

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Wed, 10 Feb 2021 00:27:04 +0200

On Sun, Jan 24, 2021 at 07:10:14PM +1100, Dmitry Smirnov wrote:
> On Saturday, 23 January 2021 6:28:09 AM AEDT Moritz Mühlenhoff wrote:
> > Indeed, the latest 8.0.23 release is now fixed:
> > | * MySQL Workbench now uses Python 3 for functionality such
> > |   as migration, scripting shell, administrative tasks, and
> > |  its SQL IDE.
> 
> Just released, thanks for letting me know. It's been just several days
> since I've checked for new release. :)
> 
> I've updated packaging for 8.0.23 but could not fix a new FTBFS problem...

Is the new FTBFS problem [1] or something else?

cu
Adrian

[1] https://github.com/antlr/antlr4/pull/3071

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

From: Dmitry Smirnov <onlyjob@debian.org>

To: 937102@bugs.debian.org, Adrian Bunk <bunk@debian.org>

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

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Wed, 10 Feb 2021 14:36:11 +1100

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

On Wednesday, 10 February 2021 9:27:04 AM AEDT Adrian Bunk wrote:
> Is the new FTBFS problem [1] or something else?
> 
> [1] https://github.com/antlr/antlr4/pull/3071

Thanks for a link. To me it looks like a new problem:

~~~~
 library/parsers/libparsers.so.8.0.23: undefined reference to `antlr4::ANTLRInputStream::ANTLRInputStream(std::basic_string_view<char, std::char_traits<char> >)'
~~~~

There is also another FTBFS problem related to MariaDB vs. MySQL but
I don't have an error message right now...

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

No snowflake in an avalanche ever feels responsible.
    -- Stanisław Jerzy Lec

---

Masks are neither effective nor safe: A summary of the science.
    -- https://www.primarydoctor.org/masks-not-effect

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

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

From: Adrian Bunk <bunk@debian.org>

To: Dmitry Smirnov <onlyjob@debian.org>

Cc: 937102@bugs.debian.org, Moritz Mühlenhoff <jmm@inutil.org>

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Wed, 10 Feb 2021 09:47:24 +0200

On Wed, Feb 10, 2021 at 02:36:11PM +1100, Dmitry Smirnov wrote:
> On Wednesday, 10 February 2021 9:27:04 AM AEDT Adrian Bunk wrote:
> > Is the new FTBFS problem [1] or something else?
> > 
> > [1] https://github.com/antlr/antlr4/pull/3071
> 
> Thanks for a link. To me it looks like a new problem:
> 
> ~~~~
>  library/parsers/libparsers.so.8.0.23: undefined reference to `antlr4::ANTLRInputStream::ANTLRInputStream(std::basic_string_view<char, std::char_traits<char> >)'
> ~~~~

Yes, I think this is just a bug in libantlr4-runtime-dev with a simple
fix to its headers.

> There is also another FTBFS problem related to MariaDB vs. MySQL but
> I don't have an error message right now...

Errors regarding MYSQL_TYPE_INVALID being undefined were the next ones I got,
I assume you know these kind of issues better.

> Regards,
>  Dmitry Smirnov

cu
Adrian

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

From: Dmitry Smirnov <onlyjob@debian.org>

To: Adrian Bunk <bunk@debian.org>, 937102@bugs.debian.org, Moritz Mühlenhoff <jmm@inutil.org>

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Thu, 11 Feb 2021 11:35:03 +1100

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

On Wednesday, 10 February 2021 6:47:24 PM AEDT Adrian Bunk wrote:
> Yes, I think this is just a bug in libantlr4-runtime-dev with a simple
> fix to its headers.

Perhaps it is simple for you but I don't understand how to address the
problem...


> Errors regarding MYSQL_TYPE_INVALID being undefined were the next ones I
> got, I assume you know these kind of issues better.

I wish I knew better but I don't... Upstream builds against MySQL and
MariaDB is not supported. We always have to improvise to build M-W
against MariaDB...

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

The end cannot justify the means for the simple and obvious reason that the
means employed determine the nature of the ends produced.
    -- Aldous Huxley

---

Masks are neither effective nor safe: A summary of the science.
    -- https://www.primarydoctor.org/masks-not-effect

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

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

From: Adrian Bunk <bunk@debian.org>

To: Dmitry Smirnov <onlyjob@debian.org>

Cc: 937102@bugs.debian.org, Moritz Mühlenhoff <jmm@inutil.org>

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Sun, 25 Jul 2021 23:37:01 +0300

On Thu, Feb 11, 2021 at 11:35:03AM +1100, Dmitry Smirnov wrote:
> On Wednesday, 10 February 2021 6:47:24 PM AEDT Adrian Bunk wrote:
> > Yes, I think this is just a bug in libantlr4-runtime-dev with a simple
> > fix to its headers.
> 
> Perhaps it is simple for you but I don't understand how to address the
> problem...

It is fixed in libantlr4-runtime-dev 4.9+dfsg-1.1 now in unstable.

> > Errors regarding MYSQL_TYPE_INVALID being undefined were the next ones I
> > got, I assume you know these kind of issues better.
> 
> I wish I knew better but I don't... Upstream builds against MySQL and
> MariaDB is not supported. We always have to improvise to build M-W
> against MariaDB...

I got 8.0.24[1] building with this new #if block removed.

If this was the last problem with 8.0.23, it might now build with
that fix.

cu
Adrian

[1] didn't find 8.0.23 upstream sources

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

From: Dmitry Smirnov <onlyjob@debian.org>

To: Adrian Bunk <bunk@debian.org>, 937102@bugs.debian.org, Moritz Mühlenhoff <jmm@inutil.org>

Subject: Re: Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

Date: Mon, 26 Jul 2021 13:48:05 +1000

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

On Monday, 26 July 2021 6:37:01 AM AEST Adrian Bunk wrote:
> It is fixed in libantlr4-runtime-dev 4.9+dfsg-1.1 now in unstable.

Awesome. Thank you very much, Adrian.
Thanks to you I've managed to build 8.0.26 and it works!
I'll upload later today.


> I got 8.0.24[1] building with this new #if block removed.

Same here. I was able to build after minor update to the existing patch.


> If this was the last problem with 8.0.23, it might now build with
> that fix.

It builds fine indeed. Thank you.


> [1] didn't find 8.0.23 upstream sources

Not sure what happened. Did they remove older release from mirrors?
Never mind, this is not a problem as we have 3 newer releases.

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

If everybody is thinking alike, then somebody isn't thinking.
 -- George S. Patton

---

Are Face Masks Effective? The Evidence.
 -- https://swprs.org/face-masks-evidence/

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

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

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

To: 937102-close@bugs.debian.org

Subject: Bug#937102: fixed in mysql-workbench 8.0.26+dfsg-1

Date: Mon, 26 Jul 2021 04:33:28 +0000

Source: mysql-workbench
Source-Version: 8.0.26+dfsg-1
Done: Dmitry Smirnov <onlyjob@debian.org>

We believe that the bug you reported is fixed in the latest version of
mysql-workbench, 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 937102@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov <onlyjob@debian.org> (supplier of updated mysql-workbench 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, 26 Jul 2021 12:38:20 +1000
Source: mysql-workbench
Architecture: source
Version: 8.0.26+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov <onlyjob@debian.org>
Changed-By: Dmitry Smirnov <onlyjob@debian.org>
Closes: 937102 944177 953138
Changes:
 mysql-workbench (8.0.26+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
     + transitioned to Python3 (Closes: #937102, #953138, #937102).
   * Removed dependency on "g++-8" (Closes: #944177).
   * Build-Depends:
     = libssh-dev (>= 0.9.5~)
     = libantlr4-runtime-dev (>= 4.9+dfsg-1.1~)
Checksums-Sha1:
 3c225d2755de34f777193224f89c8f2866e563dc 2728 mysql-workbench_8.0.26+dfsg-1.dsc
 903de2cb6fb79675b85f7f02c82fb64b0e677ae2 11560264 mysql-workbench_8.0.26+dfsg.orig.tar.xz
 3e3c68d41fae6cd7a96552306dc89158bf7ede2f 42680 mysql-workbench_8.0.26+dfsg-1.debian.tar.xz
 91355a611145c63f39f186acdea72e468b828c67 20643 mysql-workbench_8.0.26+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 0c528239c3df41728371cea4b4dac991d68298e7c8c1807f6b40e9d34b1361b5 2728 mysql-workbench_8.0.26+dfsg-1.dsc
 74d10dde27d6591567d297ae54217a4451e2d388be23e8e5c28649da52c31e81 11560264 mysql-workbench_8.0.26+dfsg.orig.tar.xz
 8809c57d8a5ebe5b1cbe82dceb35b60bad2f83f49fb36bb132e599d6385b56fd 42680 mysql-workbench_8.0.26+dfsg-1.debian.tar.xz
 d7bd786520933fd54b31c80a38f5d62c44d9c34a7a3fa31c5826d412f065d1ae 20643 mysql-workbench_8.0.26+dfsg-1_amd64.buildinfo
Files:
 1c22c46193b5f61b5a7c1d4a3c885768 2728 database optional mysql-workbench_8.0.26+dfsg-1.dsc
 49411fd7813d30e3b82f90631f196573 11560264 database optional mysql-workbench_8.0.26+dfsg.orig.tar.xz
 9d58df1077fd8c349bd5e39ed7705311 42680 database optional mysql-workbench_8.0.26+dfsg-1.debian.tar.xz
 24038201864f831c0f86af7d99eb5a41 20643 database optional mysql-workbench_8.0.26+dfsg-1_amd64.buildinfo

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

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmD+LCAACgkQUra72VOW
jRsAfBAAgmmmrJrXXjA8GJceHzKdO7f12hd0Xq8mleqdYI1UyfJk5aMaDgGWvLpl
Z16NUzU9HqexpMil6qwLDjI4yCKzwTGVmhLG3N5s0j4+lVtLj8gauk+iZiTtmYov
m59mHHiK87nTZ/ex9BGZtd7Pu8x854Dimh57e3qojuQKlteetGzBGEZfnTx6pG1S
taU9ETzMB/EF28D6/xqXt0vhfIS561X5M6Z2cFc4Gsj4iJB/BSucTdxElbrCi4vT
QQWt9Zc/TOFpqhjOyOUaQkBGAHGk/469xQ4uoWkO6fI/lYtYkPIoL2igqWVaZI48
ZZCV7+TGn4UAo63t6XH2065Qpac1nfDNUHeM3ErEsT8dPbnZzRsZR2eXbqM5nfRm
JBe20XRY53lUswKPQku6Dd95XdPNb8TxAKQr4P3mljiLnRoXr1uRFFkY3XuSTyCw
2ebAro9UiNcyEqfDGrrLvNCq71CzDYLjl9LIjFtLYkRzsHUyGIXpl9LuA4sSxYxp
+tD3McHHRddjQGr/FxEaE2Mx3lyaUTfhnRwYCF4BRj7t+WohLNXrfsqZadkf46GN
yglLaxaVpTDPmXbEu4eMUe1RxUEBrvgaRDHAYBtNEI9u4qPUFnOrtRUijHetsJX3
k7ogX+ADGmyhyxJ3Tg32tnr9EmYI/PsXqC1rQ7o9NqGGbEZOWPU=
=TUK4
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.