Bug 17192

Assigning to mysql-workbench maintainer, but also CC'ing mariadb maintainer, in case mariadb is the real culprit

CC: (none) => alien, marja11
Assignee: bugsquad => juan.baptiste
Summary: Incompatable with mariadb as supplied with - mariadb 10.0.22-1.mga => mysql-workbench-6.2.4-1.mga5 incompatable with mariadb 10.0.22-1.mga5 - Incompatible/nonstandard server version or connection protocol detected (10.0.22)

Is there anything happening with this problem?

If not then I will have to switch to using Mysql.

(In reply to Vincent Coen from comment #2)
> Is there anything happening with this problem?
> 
> If not then I will have to switch to using Mysql.

Don't know, now CC'ing all packagers collectively

CC: (none) => pkg-bugs

Well given it over 18 months so I guess the maintainers cannot resolve it.

How about giving us the option of installing mysql community instead?

At least it will get around the problem of incompatable mariadb that is supposed to be a drop in replacement for Mysql,

Not.

You're welcome to use MySQL, but we're not going to package and maintain it in Mageia ourselves.  Like you said in another bug report, hopefully updating mysql-workbench will fix this.

My usage of 'hopefully' is some what optimistic and should have used 'might'.

My primary issue with a switch to mysql instead is do I need to remove all mariadb stuff that is installed by default other than the server element?

Or if I leave that in and install ;mysql community will it make use of the hooks installed by default?

I assume here that I have to build mysql using the sources and cannot use a prebuild such as Fedora or RHEL version.

Hi Vincent,

Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue (with our newest mariadb and mysql-workbench versions) in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. Our registered MariaDB maintainer has been unavailable for quite a while, now, and we no longer have a registered mysql-workbench maintainer. If you'd like to help package & maintain mysql-workbench and/or mariadb or any other package, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

(Reassigning to all packagers collectively and CC'ing the basesystem maintainers, in case this report needs to be reopened for a supported Mageia release)

Assignee: juan.baptiste => pkg-bugs
Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => basesystem

The issue applies to Mga v6 and Workbench (v6.3.9) installed with package :  mysql-workbench-6.3.9-1.mga6 alogn with
mysql-connector-odbc
mysql-MariaDB
mysql-workbench


and mariadb v10.1.35 installed with 

mariadb-10.1.35-1.mga6
mariadb-common-10.1.35-1.mga6

and other elements for X64 such as:

lib64mariadb18
lib64mariadb-devel
mariadb-client
mariadb-common-core
mariadb-core
mariadb-extra
mariadb-feedback

Status: RESOLVED => REOPENED
CC: (none) => vbcoen
Resolution: OLD => (none)
Version: 5 => 6

Simply put, workbench has not been compiled against mariadb let alone any version of it.

Summary: mysql-workbench-6.2.4-1.mga5 incompatable with mariadb 10.0.22-1.mga5 - Incompatible/nonstandard server version or connection protocol detected (10.0.22) => mysql-workbench-6.3.9-1.mga6 incompatable with mariadb 10.1.35-1.mga6 - Incompatible/nonstandard server version or connection protocol detected (10.1.35)
Source RPM: mysql-workbench-6.2.4-1.mga5 => mysql-workbench-6.3.9-1.mga6

When I had a look at replacing mariadb with Mysql there was a large number of packages that require mariadb and would need to be removed when removing mariadb and this will create a lot of problems when trying to reload the maria dependent packages and here I do NOT mean mariadb sub elements.

This is another example for preloading dependancies during build using elements that then cannot be replaced without removing any primary libraries.

Please, please only build packages on the basis that if it does NOT need a secondary package it is not put in the rpm lists.

Hi,
Could it be linked to this problem :
https://bugs.mageia.org/show_bug.cgi?id=18475

CC: (none) => yves.brungard_mageia

No does not appear so.

It is how ever linked to bug 25071 that was fixed by a change in 
mysql-connector-c++-1.1.9-2.1.mga7

There is not a back port fix for MGA6.

Any one ?

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

Target Milestone: Mageia 5 => ---
Resolution: (none) => OLD
Status: REOPENED => RESOLVED
CC: (none) => ouaurelien

This bug was ori8ginally set for Mga v5 but was then set for v6 AND v7 as it still applies.

No doubt is will also apply to v8 as well.

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Sorry:

mysql-workbench is no longer in Cauldron as all python 2 modules get dropped

Changelog from urpmq --changelog task-obsolete | grep mysql :
- drop mysql-workbench (not ported to python3)
- drop old and python2 pkg mysql-utilities

As a community distribution, we can't have time to support thing no longer supported upstream.

Sadly closing this definitely.

Keywords: (none) => NEEDINFO
Resolution: (none) => OLD
CC: ouaurelien => (none)
Status: REOPENED => RESOLVED

The sources 8.0.21 do not specify the version of Python least of all an out of date one.

Just where are you seeing this ?

No matter, I will install Mysql in place of mariadb for all prod systems.


This issue has been around just way too long.

Says it all really :(

Vincent

This topic said that the port to Python 3 is needed:
https://forums.mysql.com/read.php?152,670986,671005
However, I didn't find any indication that this has happened.