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
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
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
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:
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
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,
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
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
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)".
--
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
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
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
>
12 matches
Mail list logo
