MariaDB in Fedora - retiring 10.3 & 10.4 series
Hello everyone, Due to several circumstances I am stopping all efforts in maintaining MariaDB 10.3 & 10.4 series in Fedora. Just before that, I rebased both series to the latest upstream versions, so you will get all the security patches released as for today ! MariaDB 10.3: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2022-0cd0202272 MariaDB 10.4: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2022-c58e1ae21e Also, please notice that neither series is available in Fedora > 35, because our efforts to cherry-pick the OpenSSL 3 patch from the 10.8 series were unsuccessful. Furthermore, please note that _on upstream_ : MariaDB 10.3 will reach 'end of standard support' and EOL on: 25 May 2023 MariaDB 10.4 reached 'end of standard support' on: 02 July 2022 and will reach EOL on: 02 July 2024 -- I strongly recommend updating your applications to at least MariaDB 10.5 series. MariaDB upstream changed it's release model some time ago [1]. The upstream expects to release a new _serie_ every three months. Every new series (starting 10.6) support period was shortened to _one year_ only. Some of the series will be marked as LTS (long term support) with support period being at least 5 years. First serie marked as LTS is 10.6 Second serie that will _likely_ be marked as LTS is 10.10 My personal focus - as the package maintainer - is on the MariaDB 10.5 ; and MariaDB 10.10 (should it be marked LTS). Please consider all other series maintained (by me in Fedora) on 'best effort' basis only. The golden rule in case of my packages is that the development is done in base Fedora (branch 'rawhide'), so whichever version there is, it is the one maintained with most care. -- As always, anyone is welcome to submit patches or (preferably) pull requests to packages I maintain, or step in to maintain MariaDB series I don't have capacity for. Feel free to ask more questions if you are interested, I'll answer what I can. I wish you a nice day and stable DB servers :) [1] https://mariadb.com/newsroom/press-releases/mariadb-announces-new-innovation-release-model/ [2] rel-eng ticket regarding setting the EOL date: https://pagure.io/releng/issue/10902 [3] Wiki page with info which series are in which Fedora releases: https://fedoraproject.org/wiki/MariaDB_software -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[MySQL & MariaDB in Fedora] MySQL 8.0 release, testers welcomed
Hello everybody! I want to share a quick overview of MySQL and MariaDB packages through Fedora. Brand new releases are available! *Available software and channels:* MariaDB 10.1 - F26 base; F27+28+Rawhide COPR MariaDB 10.2 - F27+F28+Rawhide base MariaDB 10.3 - F27+F28+Rawhide COPR MySQL 5.7 - F26+F27+F28 base MySQL 8.0 - Rawhide base The MySQL 8.0.11 <https://koji.fedoraproject.org/koji/taskinfo?taskID=26552849> is a hot new wares; MariaDB 10.3 is expected to grow GA and land in the Rawhide soon. *Modules & Containers:* Modules are in progress. In order to allow users to use alternative version of MariaDB and MySQL servers in Fedora, we're working on modular builds. In the end, users will be able to use either newer MariaDB 10.3 and MySQL 8.0, or older MariaDB 10.1 and MySQL 5.6 versions in Fedora releases where we have MariaDB 10.2 and MySQL 5.7 by default. We are trying to ship also the Fedora Containers. *Their quality right now may vary, as the infrastructure for them for both building and using is still beeing developed.* *COPR:* mschorm/mariadb-10.1 mschorm/mariadb-10.3 mschorm/mysql-8 *Connectors:* A huge amount of work was made on following packages: mariadb-connector-c mysql-connector-odbc mariadb-connector-odbc They should now work better then ever before. The connector C allowed us to divide the server and client for both usage and building dependend software. *Information, help, tutorials, tips & tricks:* Lately, I wrote several pages on the wiki, clearing up the situation: https://fedoraproject.org/wiki/Category:Package_MariaDB Are you completely new to those databases && you speak Czech? Several great articles waits for you: https://mojefedora.cz/jak-zprovoznit-mariadb-10-1-server-pro-vyvoj/ Do you have problems with the server start? "journactl -xe" or "/var/log/..." can help you. In some cases (mostly unusual re-installations) "/var/lib/mysql/" needs some cleaning. *Testing needed:* I'd love you all to try out the MySQL 8.0 and MariaDB 10.3. Explore the Copr, try out the modules, meet the container images. *I managed to prepare MySQL 5.7.22 update in less than 20 hours, but it lies in BODHI untouched.I use BODHI auto-push, so I encourage you to test them before they land in stable.* *Bugs:* File them! Let me know! My bugzilla doors are always open as well as my mail inbox :) -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: MySQL and MariaDB in Fedora
On 04/14/2013 07:10 PM, Matthias Runge wrote: On 04/14/2013 06:54 PM, Jóhann B. Guðmundsson wrote: Convincing this is about doing the right thing! I your intention was to ban mysql in the distribution then it should have been banned and dropped instead of this mess that you guys have created. IMHO you cannot ban/deprecate a package from the distro, if there's still a packager/contributor to the package. Also you can not force somebody to drop a package. I'm aware of that but we can force migration upon users on upgrades while we still provide and ship that component? If users have *chosen* to install component A and we *still* provide ( maintain,package and ship ) component A, the users should be upgraded to that components latest release upon upgrade. If users have *chosen* to install component A and we *no longer* provide ( maintain,package and ship ) component A then the argument can be made that we should migrate component A to component B during release upgrades if it provides same or similar functionality ( even thou I feel it's bad policy doing so and we would be better of doing nothing as in simply not upgrade or migrate that component unless it becomes absolutely necessary ) JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Il 15/04/2013 08:19, Jóhann B. Guðmundsson ha scritto: On 04/14/2013 07:10 PM, Matthias Runge wrote: On 04/14/2013 06:54 PM, Jóhann B. Guðmundsson wrote: Convincing this is about doing the right thing! I your intention was to ban mysql in the distribution then it should have been banned and dropped instead of this mess that you guys have created. IMHO you cannot ban/deprecate a package from the distro, if there's still a packager/contributor to the package. Also you can not force somebody to drop a package. I'm aware of that but we can force migration upon users on upgrades while we still provide and ship that component? If users have *chosen* to install component A and we *still* provide ( maintain,package and ship ) component A, the users should be upgraded to that components latest release upon upgrade. If users have *chosen* to install component A and we *no longer* provide ( maintain,package and ship ) component A then the argument can be made that we should migrate component A to component B during release upgrades if it provides same or similar functionality ( even thou I feel it's bad policy doing so and we would be better of doing nothing as in simply not upgrade or migrate that component unless it becomes absolutely necessary ) JBG +1 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/13/2013 09:42 PM, Kevin Kofler wrote: Jóhann B. Guðmundsson wrote: Users should not be switched automatically to Mariadb on upgrades Of course they should! That's the point of switching! It goes without saying that users should never be automatically moved from component A to component B if component A is still being provided, maintained and shipped in the distribution. If I installed mysql and have been running mysql then upgrade I expect the upgrade process to pick up the latest mysql we ship upgraded to that and I will be continuing to run mysql not be magically moved to fork of it mariadb. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Jóhann B. Guðmundsson wrote: It goes without saying that users should never be automatically moved from component A to component B if component A is still being provided, maintained and shipped in the distribution. Which is why IMHO MySQL should not be provided anymore at all. If I installed mysql and have been running mysql then upgrade I expect the upgrade process to pick up the latest mysql we ship upgraded to that and I will be continuing to run mysql not be magically moved to fork of it mariadb. Sorry, but the point of the MariaDB feature is that MariaDB will be the default for everyone. Just like how LibreOffice replaced OpenOffice.org, Calligra replaced KOffice, X.Org X11 replaced XFree86 etc. There are 2 possible upgrade paths for the same old software, which one we pick should be the decision of the package maintainer. Which project still carries the original name should be irrelevant. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Kevin Kofler kevin.kof...@chello.at writes: Jóhann B. Guðmundsson wrote: If I installed mysql and have been running mysql then upgrade I expect the upgrade process to pick up the latest mysql we ship upgraded to that and I will be continuing to run mysql not be magically moved to fork of it mariadb. Sorry, but the point of the MariaDB feature is that MariaDB will be the default for everyone. Just like how LibreOffice replaced OpenOffice.org, Calligra replaced KOffice, X.Org X11 replaced XFree86 etc. It's worth pointing out here that the Oracle folk are intent on pushing that package to mysql 5.6 ASAP. (Honza and I have been recommending to them that they wait till the F20 timeframe, just to reduce the amount of change happening in F19, but in any case it's coming pretty darn soon.) At that point mariadb 5.5 will actually be the lesser-change option for people currently using mysql 5.5. So I don't find Jóhann's argument terribly convincing. There is no no-change update path on the table, and the path that we are making the default requires less change than the other one. So that seems to me to be the right thing; arguments based on the name of the package are pretty off-topic. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/14/2013 03:11 PM, Tom Lane wrote: Kevin Kofler kevin.kof...@chello.at writes: Jóhann B. Guðmundsson wrote: If I installed mysql and have been running mysql then upgrade I expect the upgrade process to pick up the latest mysql we ship upgraded to that and I will be continuing to run mysql not be magically moved to fork of it mariadb. Sorry, but the point of the MariaDB feature is that MariaDB will be the default for everyone. Just like how LibreOffice replaced OpenOffice.org, Calligra replaced KOffice, X.Org X11 replaced XFree86 etc. It's worth pointing out here that the Oracle folk are intent on pushing that package to mysql 5.6 ASAP. (Honza and I have been recommending to them that they wait till the F20 timeframe, just to reduce the amount of change happening in F19, but in any case it's coming pretty darn soon.) At that point mariadb 5.5 will actually be the lesser-change option for people currently using mysql 5.5. So I don't find Jóhann's argument terribly convincing. There is no no-change update path on the table, and the path that we are making the default requires less change than the other one. So that seems to me to be the right thing; arguments based on the name of the package are pretty off-topic. Convincing this is about doing the right thing! I your intention was to ban mysql in the distribution then it should have been banned and dropped instead of this mess that you guys have created. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/14/2013 06:54 PM, Jóhann B. Guðmundsson wrote: Convincing this is about doing the right thing! I your intention was to ban mysql in the distribution then it should have been banned and dropped instead of this mess that you guys have created. IMHO you cannot ban/deprecate a package from the distro, if there's still a packager/contributor to the package. Also you can not force somebody to drop a package. -- Matthias Runge mru...@matthias-runge.de -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Matthias Runge wrote: IMHO you cannot ban/deprecate a package from the distro, if there's still a packager/contributor to the package. Also you can not force somebody to drop a package. FESCo has done that even to a whole group of packages: (separately-packaged) kernel modules! It would make much more sense to do that here than there. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Hi On Sun, Apr 14, 2013 at 7:31 PM, Kevin Kofler wrote: Matthias Runge wrote: IMHO you cannot ban/deprecate a package from the distro, if there's still a packager/contributor to the package. Also you can not force somebody to drop a package. FESCo has done that even to a whole group of packages: (separately-packaged) kernel modules! It would make much more sense to do that here than there. Kevin, You aren't going to convince anyone by repeating yourself constantly. Kindly stop. Thanks Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
Jóhann B. Guðmundsson wrote: Users should not be switched automatically to Mariadb on upgrades Of course they should! That's the point of switching! Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 05/04 23.18, Matthias Runge wrote: On 04/05/2013 08:06 PM, Norvald Ryeng wrote: How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. About updating: https://fedoraproject.org/wiki/Updates_Policy and how to join the package collection maintainers: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers I have previously announced here that I plan to do this once the necessary package details have been settled. This was put on hold due to the uncertainties around package names etc. Thanks for the link, I am reading through it now. Regards, -- Bjorn Munch, MySQL Release Engineering, Oracle Trondheim, Norway -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
- hho...@redhat.com wrote: On 04/10/2013 02:34 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 04/05/2013 08:06 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. I wanted to use that, but then found out that it wouldn't work. The problem is that it has the same prefix as virtual name mysql, that is used as requirement in other packages. As a result, when somebody asked for mysql -- mysql-community would be preferred before mariadb, because according [1] rule #9 (check the prefix of the pkg to the requiring pkg prefix (perl-foo and perl-lib) for each common character in the prefix add 2 points to the provider's score) would be applied. When we use the name community-mysql we don't have any same prefix, so the rule #10 is applied (if, at this point, we have pkgs with an equal score - look at the version of the provide), which means mariadb with higher epoch will be chosen. We've tested and found that if the MariaDB packages have a higher epoch number, they will be chosen even if the MySQL packages have a mysql-community prefix. According to what I read in [1], mysql-community would be preferred before mariadb because of common prefix, in case both packages will have the same score from the previous rules. I've tested that with a potential package mysqlfoo, which has the same prefix as mysql-community, so if I ran: $ yum update mysqlfoo then mysql-community got higher score and was preferred before mariadb. Maybe there are even more cases like that, so I'd rather stick with community-mysql. [1] http://yum.baseurl.org/wiki/CompareProviders We've tested and retested. With versioned provides and epoch bump, MariaDB is preferred, regardless of the name of the MySQL packages. Generally, I don't like either, that packages in openSUSE an Fedora won't have the same name, but openSUSE has a bit more powerful RPM spec to handle such things. [1] http://yum.baseurl.org/wiki/CompareProviders How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others * better wait a bit longer to stabilize the new release than bring a quite important package too soon Introduction of MariaDB should not interfere with upgrading MySQL. If anything, choosing MariaDB as the default makes upgrading MySQL easier since it will only be installed when users explicitly ask for it. Upgrades like this are usually considered as a Feature, which also corresponds with Feature description at [2]. Therefore I'd rather wait for F20. [2] https://fedoraproject.org/wiki/Features/Policy/Definitions Since MariaDB is now the default, I don't see how MySQL upgrades need a feature request by these definitions. If you look at the feature request history, there are only a few upgrade features. Most software is upgraded without a feature request. I couldn't find any feature requests for previous MySQL upgrades. Regards, Norvald H. Ryeng -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
- hho...@redhat.com wrote: On 04/05/2013 08:06 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. I wanted to use that, but then found out that it wouldn't work. The problem is that it has the same prefix as virtual name mysql, that is used as requirement in other packages. As a result, when somebody asked for mysql -- mysql-community would be preferred before mariadb, because according [1] rule #9 (check the prefix of the pkg to the requiring pkg prefix (perl-foo and perl-lib) for each common character in the prefix add 2 points to the provider's score) would be applied. When we use the name community-mysql we don't have any same prefix, so the rule #10 is applied (if, at this point, we have pkgs with an equal score - look at the version of the provide), which means mariadb with higher epoch will be chosen. We've tested and found that if the MariaDB packages have a higher epoch number, they will be chosen even if the MySQL packages have a mysql-community prefix. Generally, I don't like either, that packages in openSUSE an Fedora won't have the same name, but openSUSE has a bit more powerful RPM spec to handle such things. [1] http://yum.baseurl.org/wiki/CompareProviders How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others * better wait a bit longer to stabilize the new release than bring a quite important package too soon Introduction of MariaDB should not interfere with upgrading MySQL. If anything, choosing MariaDB as the default makes upgrading MySQL easier since it will only be installed when users explicitly ask for it. Regards, Norvald H. Ryeng -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/10/2013 02:34 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 04/05/2013 08:06 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. I wanted to use that, but then found out that it wouldn't work. The problem is that it has the same prefix as virtual name mysql, that is used as requirement in other packages. As a result, when somebody asked for mysql -- mysql-community would be preferred before mariadb, because according [1] rule #9 (check the prefix of the pkg to the requiring pkg prefix (perl-foo and perl-lib) for each common character in the prefix add 2 points to the provider's score) would be applied. When we use the name community-mysql we don't have any same prefix, so the rule #10 is applied (if, at this point, we have pkgs with an equal score - look at the version of the provide), which means mariadb with higher epoch will be chosen. We've tested and found that if the MariaDB packages have a higher epoch number, they will be chosen even if the MySQL packages have a mysql-community prefix. According to what I read in [1], mysql-community would be preferred before mariadb because of common prefix, in case both packages will have the same score from the previous rules. I've tested that with a potential package mysqlfoo, which has the same prefix as mysql-community, so if I ran: $ yum update mysqlfoo then mysql-community got higher score and was preferred before mariadb. Maybe there are even more cases like that, so I'd rather stick with community-mysql. [1] http://yum.baseurl.org/wiki/CompareProviders Generally, I don't like either, that packages in openSUSE an Fedora won't have the same name, but openSUSE has a bit more powerful RPM spec to handle such things. [1] http://yum.baseurl.org/wiki/CompareProviders How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others * better wait a bit longer to stabilize the new release than bring a quite important package too soon Introduction of MariaDB should not interfere with upgrading MySQL. If anything, choosing MariaDB as the default makes upgrading MySQL easier since it will only be installed when users explicitly ask for it. Upgrades like this are usually considered as a Feature, which also corresponds with Feature description at [2]. Therefore I'd rather wait for F20. [2] https://fedoraproject.org/wiki/Features/Policy/Definitions Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On Mon, 08 Apr 2013 09:38:53 +0200 Honza Horak hho...@redhat.com wrote: ...snip... How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers If any of the existing maintainers of the package are willing to mentor you, you could also use: http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer as a quicker way to get involved in just those packages. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/05/2013 08:06 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. I wanted to use that, but then found out that it wouldn't work. The problem is that it has the same prefix as virtual name mysql, that is used as requirement in other packages. As a result, when somebody asked for mysql -- mysql-community would be preferred before mariadb, because according [1] rule #9 (check the prefix of the pkg to the requiring pkg prefix (perl-foo and perl-lib) for each common character in the prefix add 2 points to the provider's score) would be applied. When we use the name community-mysql we don't have any same prefix, so the rule #10 is applied (if, at this point, we have pkgs with an equal score - look at the version of the provide), which means mariadb with higher epoch will be chosen. Generally, I don't like either, that packages in openSUSE an Fedora won't have the same name, but openSUSE has a bit more powerful RPM spec to handle such things. [1] http://yum.baseurl.org/wiki/CompareProviders How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others * better wait a bit longer to stabilize the new release than bring a quite important package too soon Regards, Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/08/2013 07:38 AM, Honza Horak wrote: However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze Yes thanks to how you have handled this * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others Users should not be switched automatically to Mariadb on upgrades * better wait a bit longer to stabilize the new release than bring a quite important package too soon like we do with the rest of the components in the distribution. shrug JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
- hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. Regards, Norvald H. Ryeng -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/05/2013 08:06 PM, Norvald Ryeng wrote: Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. https://fedoraproject.org/wiki/Package_Renaming_Process also naming rules apply https://fedoraproject.org/wiki/Packaging:NamingGuidelines How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. About updating: https://fedoraproject.org/wiki/Updates_Policy and how to join the package collection maintainers: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers -- Matthias Runge mru...@matthias-runge.de -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
On 01/16/2013 10:07 AM, Henrique Junior wrote: Other distros are discussing about the future of MySQL and the implementation of MariaDB as default. What is Fedora position about this matter? Got any links to those other distributions discussions JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
On Wed, Jan 16, 2013 at 08:07:30AM -0200, Henrique Junior wrote: Other distros are discussing about the future of MySQL and the implementation of MariaDB as default. What is Fedora position about this matter? There have been a few threads about this. We need facts to get a decision - such a fact would be a mariadb package review with a package that replaces mysql. I've started working on such a package for few months ago but haven't made any significant advances due to personal time constraints. So if anyone else would like to work on this. -- sven === jabber/xmpp: s...@lankes.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
On Wed, Jan 16, 2013 at 8:07 AM, Henrique Junior henrique...@gmail.com wrote: Other distros are discussing about the future of MySQL and the implementation of MariaDB as default. What is Fedora position about this matter? -- Henrique LonelySpooky Junior http://about.me/henriquejunior I think this is going to happen for F19 or F20 http://koji.fedoraproject.org/koji/packageinfo?packageID=15262 Itamar Reis Peixoto -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
Amazing Can it replace mysql in the future? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
On Wed, Jan 16, 2013 at 08:44:31AM -0200, Itamar Reis Peixoto wrote: [MariaDB] I think this is going to happen for F19 or F20 http://koji.fedoraproject.org/koji/packageinfo?packageID=15262 Great news - I totally missed this. This is the package review: https://bugzilla.redhat.com/show_bug.cgi?id=875150 -- sven === jabber/xmpp: s...@lankes.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
Henrique Junior henrique...@gmail.com writes: Other distros are discussing about the future of MySQL and the implementation of MariaDB as default. What is Fedora position about this matter? https://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB We could use help with testing. Personally I'd like to dump mysql in time for F19, but we need validation that switching to maria doesn't break anything for anyone. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MariaDB in Fedora
On 01/16/2013 04:55 PM, Tom Lane wrote: https://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB We could use help with testing. Personally I'd like to dump mysql in time for F19, but we need validation that switching to maria doesn't break anything for anyone. Good news guys! I'll give OpenStack a shot. -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
