Bug 1580061

Summary:	MySQL doesn't work
Product:	[Fedora] Fedora	Reporter:	Jeremy Newton <alexjnewt>
Component:	sequeler	Assignee:	Fabio Valentini <decathorpe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	decathorpe
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-27 16:47:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1423852
Bug Blocks:

Description Jeremy Newton 2018-05-19 18:14:20 UTC

When I try to connect to a mysql db, I get this error:

 No provider 'MySQL' installed

it seems I'm not the only one, see the upstream bug:
https://github.com/Alecaddd/sequeler/issues/26#issuecomment-372462711

It seems to work fine with the flathub flatpak version, so I think this is a packaging bug.

Comment 1 Fabio Valentini 2018-05-19 18:16:03 UTC

No, this is because libgda is broken and outdated in fedora, and the MySQL backend isn't compatible with the available mariadb anymore.

Comment 2 Jeremy Newton 2018-05-19 18:32:26 UTC

Ah, is there a bug for it? If so can you add it as a blocker for this?

Comment 3 Fabio Valentini 2018-05-19 18:36:24 UTC

Sure!

Comment 4 Jeremy Newton 2018-05-19 18:45:45 UTC

Thanks Fabio! I'll followup with the maintainer if I have some free time.

Comment 5 Ben Cotton 2018-11-27 15:40:19 UTC

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fabio Valentini 2018-11-27 15:57:03 UTC

This bug is still valid on all fedora releases, and is still blocked by the broken libgda builds in fedora. So, re-tagging with "rawhide".

Comment 7 Fabio Valentini 2018-12-06 20:38:17 UTC

This should now be fixed with the latest libgda update in fedora 29.

Comment 8 Ben Cotton 2019-02-19 17:12:04 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.