info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Debian 12 vs MySql WOrkbench
68 views
Skip to first unread message
Allan Frank
Nov 21, 2023, 4:00:04 AM11/21/23
to
Hi Linux Debian 12
Im a student and I use Debian 12 and in general very happy for that.
Now according my edducation I need MySql Workbench, but as I see its in
status "unstable" to Debian 12.
Is there any fix for that issues in the near future ??
Yes, I can use a ViatuelBox and have a whole other system there, but
its not optimal.
Let me hear from you, if there is any tips/fix or something I can do,
that make the MySql Workbench work on Debian 12.
Kind regards
Allan Frank
It-Arkitechtur
IBA - Kolding
Im a student and I use Debian 12 and in general very happy for that.
Now according my edducation I need MySql Workbench, but as I see its in
status "unstable" to Debian 12.
Is there any fix for that issues in the near future ??
Yes, I can use a ViatuelBox and have a whole other system there, but
its not optimal.
Let me hear from you, if there is any tips/fix or something I can do,
that make the MySql Workbench work on Debian 12.
Kind regards
Allan Frank
It-Arkitechtur
IBA - Kolding
Steffen Möller
Nov 21, 2023, 5:40:04 AM11/21/23
to
Hi Allan,
The status of the package is described on
https://tracker.debian.org/pkg/mysql-workbench
and you see it is waiting for another package to transition to testing, so it can migrate itself.
The bug it depends on is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040290
and it is already fixed for several months, just apparently the maintainers did not get around to reupload a fixed version.
No idea how to speed this up. Man power is a thing. If you are using Debian on your very own hardware then I suggest to just use unstable, really. This is where you can run the very latest versions (why typically are just as good as what uptream provides), find problems and confirm fixes to work. And why not maintain a package of your interest yourself?
Steffen
> Gesendet: Dienstag, 21. November 2023 um 08:25 Uhr
> Von: "Allan Frank" <allan....@icloud.com>
> An: debian-...@lists.debian.org
> Betreff: Debian 12 vs MySql WOrkbench
The status of the package is described on
https://tracker.debian.org/pkg/mysql-workbench
and you see it is waiting for another package to transition to testing, so it can migrate itself.
The bug it depends on is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040290
and it is already fixed for several months, just apparently the maintainers did not get around to reupload a fixed version.
No idea how to speed this up. Man power is a thing. If you are using Debian on your very own hardware then I suggest to just use unstable, really. This is where you can run the very latest versions (why typically are just as good as what uptream provides), find problems and confirm fixes to work. And why not maintain a package of your interest yourself?
Steffen
> Gesendet: Dienstag, 21. November 2023 um 08:25 Uhr
> Von: "Allan Frank" <allan....@icloud.com>
> An: debian-...@lists.debian.org
> Betreff: Debian 12 vs MySql WOrkbench
Andrey Rakhmatullin
Nov 21, 2023, 8:40:06 AM11/21/23
to
On Tue, Nov 21, 2023 at 11:35:46AM +0100, Steffen Möller wrote:
> Hi Allan,
>
> The status of the package is described on
> https://tracker.debian.org/pkg/mysql-workbench
>
> and you see it is waiting for another package to transition to testing, so it can migrate itself.
>
> The bug it depends on is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040290
> and it is already fixed for several months, just apparently the maintainers did not get around to reupload a fixed version.
(the user asked about Debian 12 which is stable)
> Hi Allan,
>
> The status of the package is described on
> https://tracker.debian.org/pkg/mysql-workbench
>
> and you see it is waiting for another package to transition to testing, so it can migrate itself.
>
> The bug it depends on is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040290
> and it is already fixed for several months, just apparently the maintainers did not get around to reupload a fixed version.
0 new messages