Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 std::char_traits >)' > 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
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 >)' 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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
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 Description: This is a digitally signed message part.
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:27:37AM +, Matthias Klose wrote: > Package: src:mysql-workbench > Version: 8.0.17+dfsg-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@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
