This is the last effective blocker for dev-python/paramiko.
The latest version, 8.0.19, actively fails with python 3.6, so this will need patches from someone knowing Python or a new upstream release which fixes this.
Version 8.0.20 still fails, and upstream gives no indication they are working on it: see their forum post https://forums.mysql.com/read.php?152,685111,686562#msg-686562
At least there is a bug filed for this: https://bugs.mysql.com/bug.php?id=98839. Status is "verified" but there has been no activity.
ping.
(In reply to Michał Górny from comment #4) > ping. Looks like there is nothing we can do here without upstream working on it. From the brief look I had at it it is not a quick fix that we could apply in a patch given that the code compiles against python header files. I'd say to leave this in the tree until upstream finally moves on this, but I assume the dependencies on pexpect and paramiko make this difficult.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7db99d87e8cbce1345895fa416e78d2dba29b258 commit 7db99d87e8cbce1345895fa416e78d2dba29b258 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-09-21 06:13:31 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-09-21 06:15:13 +0000 dev-db/mysql-workbench: Remove last-rited pkg Closes: https://bugs.gentoo.org/715172 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-db/mysql-workbench/Manifest | 4 - .../files/mysql-workbench-6.2.5-wbcopytables.patch | 12 -- .../mysql-workbench-8.0.19-mysql-connector-8.patch | 12 -- .../mysql-workbench-8.0.21-boost-1.73.0.patch | 123 --------------------- dev-db/mysql-workbench/metadata.xml | 10 -- .../mysql-workbench-8.0.19-r1.ebuild | 109 ------------------ .../mysql-workbench/mysql-workbench-8.0.20.ebuild | 109 ------------------ .../mysql-workbench/mysql-workbench-8.0.21.ebuild | 110 ------------------ profiles/package.mask | 1 - 9 files changed, 490 deletions(-)
But it's removed from the portage tree, mysql-workbench is a useful tool (In reply to Larry the Git Cow from comment #6) > The bug has been closed via the following commit(s): > > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=7db99d87e8cbce1345895fa416e78d2dba29b258 > > commit 7db99d87e8cbce1345895fa416e78d2dba29b258 > Author: Michał Górny <mgorny@gentoo.org> > AuthorDate: 2020-09-21 06:13:31 +0000 > Commit: Michał Górny <mgorny@gentoo.org> > CommitDate: 2020-09-21 06:15:13 +0000 > > dev-db/mysql-workbench: Remove last-rited pkg > > Closes: https://bugs.gentoo.org/715172 > Signed-off-by: Michał Górny <mgorny@gentoo.org> > > dev-db/mysql-workbench/Manifest | 4 - > .../files/mysql-workbench-6.2.5-wbcopytables.patch | 12 -- > .../mysql-workbench-8.0.19-mysql-connector-8.patch | 12 -- > .../mysql-workbench-8.0.21-boost-1.73.0.patch | 123 > --------------------- > dev-db/mysql-workbench/metadata.xml | 10 -- > .../mysql-workbench-8.0.19-r1.ebuild | 109 ------------------ > .../mysql-workbench/mysql-workbench-8.0.20.ebuild | 109 ------------------ > .../mysql-workbench/mysql-workbench-8.0.21.ebuild | 110 ------------------ > profiles/package.mask | 1 - > 9 files changed, 490 deletions(-)
(In reply to Igor Franchuk from comment #7) > But it's removed from the portage tree, mysql-workbench is a useful tool Once mysql-workbench supports python 3 we can consider bringing it back.
For me as a developer mysql-workbench is a must tool, I can't do without it. I wish to us all that you could bring it back into the portage. mySQL-Workbench is a powerful tool which is not dead and actively developed. And mySQL is the most popular database engine in the world and workbench is it's main developing platform. (In reply to Hans de Graaff from comment #8) > (In reply to Igor Franchuk from comment #7) > > But it's removed from the portage tree, mysql-workbench is a useful tool > > Once mysql-workbench supports python 3 we can consider bringing it back.
pytheon 2.7 dependency seems to be ironed out in 8.0.23 https://github.com/mysql/mysql-workbench/commit/862ac84eec4518df8bd8924b86468a9a423ce9f2
(In reply to Till Schäfer from comment #10) > pytheon 2.7 dependency seems to be ironed out in 8.0.23 > > https://github.com/mysql/mysql-workbench/commit/ > 862ac84eec4518df8bd8924b86468a9a423ce9f2 Yes, I'm seeing them declaring Python >= 3.7 as dependency for Fedora's source RPM. And I am able to build 8.0.23 with this ebuild modified by me based on the last official ebuild for 8.0.21: https://gist.github.com/Leo3418/a4049dd4caea892eda5bca20efe66eda
(In reply to "Leo" Y. Liao from comment #11) > (In reply to Till Schäfer from comment #10) > > pytheon 2.7 dependency seems to be ironed out in 8.0.23 > > > > https://github.com/mysql/mysql-workbench/commit/ > > 862ac84eec4518df8bd8924b86468a9a423ce9f2 > > Yes, I'm seeing them declaring Python >= 3.7 as dependency for Fedora's > source RPM. And I am able to build 8.0.23 with this ebuild modified by me > based on the last official ebuild for 8.0.21: > https://gist.github.com/Leo3418/a4049dd4caea892eda5bca20efe66eda Confirmed.
8.0.23 doesn't compile out of the box for me, due to libssh incompatibilities. For those of you that compiled 8.0.23 succesfully, which version of libssh did you use at the time of compilation? (it seems to be a build-time issue, so current run-time doesn't matter).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1896841452356d6598b3c5ce21131ecd260790db commit 1896841452356d6598b3c5ce21131ecd260790db Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2021-02-21 10:38:11 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2021-02-21 10:38:28 +0000 dev-db/mysql-workbench: re-import of 8.0.23 Add mysql-workbench back now that it is compatible with python 3. Bug: https://bugs.gentoo.org/715172 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-db/mysql-workbench/Manifest | 2 + .../files/mysql-workbench-6.2.5-wbcopytables.patch | 12 +++ .../mysql-workbench-8.0.19-mysql-connector-8.patch | 12 +++ .../files/mysql-workbench-8.0.23-findlibssh.patch | 11 ++ dev-db/mysql-workbench/metadata.xml | 10 ++ .../mysql-workbench/mysql-workbench-8.0.23.ebuild | 112 +++++++++++++++++++++ 6 files changed, 159 insertions(+)
(In reply to Hans de Graaff from comment #13) > 8.0.23 doesn't compile out of the box for me, due to libssh > incompatibilities. For those of you that compiled 8.0.23 succesfully, which > version of libssh did you use at the time of compilation? (it seems to be a > build-time issue, so current run-time doesn't matter). In my case: net-libs/libssh-0.9.5
