On 06/21/2017, 10:21 AM, Robert Munteanu wrote:

I need to look into alternatives.

What's wrong with mariadb? -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Robert Munteanu wrote:

On Wed, Jun 21, 2017 at 12:34 PM, Jiri Slaby wrote:

...

On 06/21/2017, 10:21 AM, Robert Munteanu wrote:

...

I need to look into alternatives. What's wrong with mariadb? For me personally, it's SonarQube not supporting it.

https://groups.google.com/forum/#!topic/sonarqube/32x5fsWHfCQ I am also disappointed about the fact, that MySQL is removed from TW.

One possible alternative can be the MySQL Community Server packages from www.mysql.com. Unfortunately they are build for SUSE Linux Enterprise Server. Currently these packages run on TW, but this is not guarantied. All the MySQL and MariaDB packages for SUSE/openSUSE are build from https://github.com/openSUSE/mysql-packaging. Unfortunately the build scripts and the workflow are complex, which makes contributing difficult. One of the possible ways to get MySQL back to TW can be: 1. Make mysql-community-server-57 packages (Oracle packages for SLES) compatible with TW 2. Build and test such packages in repository server:database (the old broken version 5.7.7 is the latest there) 3. Copy the packages back to the official TW repositories Personally I don't see a future for the MySQL 5.6.x packages. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 22 June 2017 at 11:39, Bjoern Voigt wrote:

Dominique Leuenberger / DimStar wrote:

...

Message: Noone is interested in maintaining this anymore. How much extra work is it to maintain MySQL for Tumbleweed? MySQL must be maintained for SLES and Leap anyway.

MySQL is not available in SLES 12 https://www.suse.com/LinuxPackages/packageRouter.jsp?product=server&version=12&service_pack=&architecture=x86_64&package_name=index_all Therefore your assumption that MySQL must be maintained for SLES and Leap is invalid, Dominique's point remains: If someone wishes to maintain a MySQL package in the openSUSE distributions, someone needs to do the work. Regards, Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 22 June 2017 at 12:23, Bjoern Voigt wrote:

Richard Brown wrote:

...

On 22 June 2017 at 11:39, Bjoern Voigt wrote:

...

Dominique Leuenberger / DimStar wrote:

...

Message: Noone is interested in maintaining this anymore. How much extra work is it to maintain MySQL for Tumbleweed? MySQL must be maintained for SLES and Leap anyway. MySQL is not available in SLES 12

https://www.suse.com/LinuxPackages/packageRouter.jsp?product=server&version=12&service_pack=&architecture=x86_64&package_name=index_all

Therefore your assumption that MySQL must be maintained for SLES and Leap is invalid, Dominique's point remains: If someone wishes to maintain a MySQL package in the openSUSE distributions, someone needs to do the work. No, MySQL is officially available for SLES 12: https://dev.mysql.com/downloads/mysql/

These packages are not 'offical' SUSE or openSUSE packages They are provided by Oracle/MySQL, from Oracle/MySQL servers. If you want Oracle to add Tumbleweed support to their packages, I would suggest you contact them.

The Oracle and SUSE/openSUSE MySQL repositories are connected, because all are based on the same Gibhub project. The build service repositories use generated RPM files from this project: https://github.com/openSUSE/mysql-packaging

I do not see how you establish a link between the mysql-packaging github project. I am under the impression that generator is used to generate our mariadb specfile used for our mariadb packages in openSUSE. If the rpms produced by Oracle/MySQL on the URL you provided above also use the same generator, that's cool, but shouldn't be read that they somehow magically become official SUSE/openSUSE packages in that case. The only official source of SUSE packages is SUSE's repositories, and the only official source of openSUSE packages is openSUSE's repositories, each signed with the respective GPG key of their respective organisations.

I would take over this work, but last time I had some problems with the generation scripts, so I would need some more experience with them.

Well I think it would be cool if you try, you definitely need to be sure about the details of what you're getting yourself into. Good luck! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 6/22/17 8:49 PM, Bjoern Voigt wrote:

Richard Brown wrote:

...

These packages are not 'offical' SUSE or openSUSE packages

They are provided by Oracle/MySQL, from Oracle/MySQL servers. If you want Oracle to add Tumbleweed support to their packages, I would suggest you contact them.

...

...

The Oracle and SUSE/openSUSE MySQL repositories are connected, because all are based on the same Gibhub project. The build service repositories use generated RPM files from this project: https://github.com/openSUSE/mysql-packaging I do not see how you establish a link between the mysql-packaging github project. I am under the impression that generator is used to generate our mariadb specfile used for our mariadb packages in openSUSE. Look at this: https://lists.opensuse.org/opensuse-factory/2016-12/msg00266.html

That does not explain how "The Oracle and SUSE/openSUSE MySQL repositories are connected" - there is zero relation between rpms provided by oracle and openSUSE mysql-packaging github project. This project serves purpose of sharing common parts of spec files/patches between different versions of MariaDB and MySQL (MySQL community edition). I am really not sure which other repositories are you talking about, both MySQL and MariaDB are developed in server:database, thus they come from same repository. I would also like to avoid any potential confusion - openSUSE never provided supported "Oracle MySQL", only community edition of MySQL. Last but not least, apart from referencing support statements by third party software, and stating lack of interest in switching from MySQL to MariaDB I have not seen any technical (as in missing functionality) reason to keep MySQL (whose development is anyways limited nowadays, and Oracle's shift to providing only cloud services, not software is making this questionable investment of time/resources anyways). That being sad anybody interested in keeping MySQL in Factory is of course free to do so. Regards Martin

On Thu, 2017-06-22 at 11:39 +0200, Bjoern Voigt wrote:

Dominique Leuenberger / DimStar wrote:

...

Message: Noone is interested in maintaining this anymore.

How much extra work is it to maintain MySQL for Tumbleweed? MySQL must be maintained for SLES and Leap anyway.

Must it? If you talk SLE12/Leap 42.x, then yes, but keep in mind that TW moved to GCC7 and also a lot of other things progressed. I guess if somebody establishes a working relationship with upstream it should not be that much effort to keep it running once it is back in usable shape. I can't estimate though how much work it will be to get it back in shape for TW. Cheers, Dominique