[opensuse-factory] consolidating the list of mysql flavors in Factory
Hi, at the moment we seem to have the following mysql flavors in Factory: mysql-community-server mysql-cluster mariadb There might be more that I don't know about. Given that mysql is a package that needs frequent updating (both for security and for non-security bugfix reasons); I was wondering if it really makes sense to have multiple flavors of it in Factory (and thereby in openSUSE 12.1). We did so in the past for 11.3 and 11.4, and noticed that this was a problem (security updates took look to be submitted, and then they had major regressions that broke severly). So, my question is twofold: - is there anyone stepping up to maintain mariadb and mysql-cluster for the full openSUSE lifetime? - if no, who would object (and why) to dropping those variants from factory? Note that the other flavors can still be in server:database, even built for older distros, so those who really want it can use it. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Thu, 25 Aug 2011 13:26:59 +0200 schrieb Dirk Müller <dmueller@suse.de>:
at the moment we seem to have the following mysql flavors in Factory:
mysql-community-server mysql-cluster mariadb
- if no, who would object (and why) to dropping those variants from factory?
What are the differences between the three packages? -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am 25.08.2011 21:25, schrieb Stefan Seyfried:
Am Thu, 25 Aug 2011 13:26:59 +0200 schrieb Dirk Müller <dmueller@suse.de>:
at the moment we seem to have the following mysql flavors in Factory:
mysql-community-server mysql-cluster mariadb
- if no, who would object (and why) to dropping those variants from factory?
What are the differences between the three packages?
I've lost the original mail apparently but IMHO all these are still interesting and relevant. mysql-cluster is a completely different thing than the others. mysql-community-server and mariadb are (should be) drop-in replacements for each other http://kb.askmonty.org/en/mariadb-versus-mysql And I'd find it useful to have one alternative to "the original mysql". Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 25/08/11 08:26, Dirk Müller wrote:
Hi,
at the moment we seem to have the following mysql flavors in Factory:
mysql-community-server mysql-cluster mariadb
There might be more that I don't know about. Given that mysql is a package that needs frequent updating (both for security and for non-security bugfix reasons); I was wondering if it really makes sense to have multiple flavors of it in Factory (and thereby in openSUSE 12.1). We did so in the past for 11.3 and 11.4, and noticed that this was a problem (security updates took look to be submitted, and then they had major regressions that broke severly).
So, my question is twofold:
- is there anyone stepping up to maintain mariadb and mysql-cluster for the full openSUSE lifetime?
- if no, who would object (and why) to dropping those variants from factory?
Note that the other flavors can still be in server:database, even built for older distros, so those who really want it can use it.
Thanks, Dirk
I would rather drop mysql-community-server than mariadb which is esentially an improved version of the former that uses either backports or custom tailored fixes. Not having to deal with Oracle is also a plus. ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 25 August 2011, Cristian Rodríguez wrote:
I would rather drop mysql-community-server than mariadb which is esentially an improved version of the former that uses either backports or custom tailored fixes.
Possible, I don't have a preference between those two, except that the mariadb package seems to be nonworking at the moment (trying factory with empty dir, the init script aborts becasue the initial database setup fails).
Not having to deal with Oracle is also a plus. ;)
as this is the community edition, I don't think we have to deal with Oracle in any way. The big plus is that Oracle maintains this version for us, so the only thing to do to fix security / bugs is usually to do a patchlevel version update. I'm not sure if the same applies to mariadb. My main point is: choose one, please. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/26/2011 09:52 AM, Dirk Müller wrote:
On Thursday 25 August 2011, Cristian Rodríguez wrote:
I would rather drop mysql-community-server than mariadb which is esentially an improved version of the former that uses either backports or custom tailored fixes.
Possible, I don't have a preference between those two, except that the mariadb package seems to be nonworking at the moment (trying factory with empty dir, the init script aborts becasue the initial database setup fails).
Not having to deal with Oracle is also a plus. ;)
as this is the community edition, I don't think we have to deal with Oracle in any way. The big plus is that Oracle maintains this version for us, so the only thing to do to fix security / bugs is usually to do a patchlevel version update.
I'm not sure if the same applies to mariadb. My main point is: choose one, please.
Thanks, Dirk
Dirk to be able to (for example) drop mysql-community version, we need to test all mysql linked software against mariadb. So first enable a long (I suspect very long) list of those software. Perhaps there's a hook somewhere in obs, able to auto-build those deps. Then test carefully, one by one, to be sure there's no big failure or regression with mariadb. and notice any changes or optimization needed to be applied by admins (db conversion etc) in a long readme. Would be nice to have to support only one. But I've a doubt about the pure drop'in replacement. It's not like replacing cron by cronie ... There's user data involved in that case. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 26 August 2011, Bruno Friedmann wrote:
Dirk to be able to (for example) drop mysql-community version, we need to test all mysql linked software against mariadb. So first enable a long (I suspect very long) list of those software. Perhaps there's a hook somewhere in obs, able to auto-build those deps.
Then test carefully, one by one, to be sure there's no big failure or regression with mariadb. and notice any changes or optimization needed to be applied by admins (db conversion etc) in a long readme.
Would be nice to have to support only one. But I've a doubt about the pure drop'in replacement. It's not like replacing cron by cronie ... There's user data involved in that case.
Hi Bruno, If I would follow your steps, then that means that at one particular point in time we have "certified" that it works. What does that help? how does that help with any fast moving target like openSUSE Factory where things are constantly being updated, repackaged, etc? I think focusing on what is maintainable is more important: What can be fixed easily when it has a problem? Can we get mariadb developers to priotize fixes for data loss or critical performance issues? Can we get that for mysql community server? My guess is that for both the answer is "nay", which means that we can pick one over the other. I don't care which one, please just make the issue of maintaining a database (and "supporting" it in the sense of how opensuse is supported) more difficult by providing multiple flavors of it. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 09/14/2011 10:46 AM, Dirk Müller wrote:
On Friday 26 August 2011, Bruno Friedmann wrote:
Dirk to be able to (for example) drop mysql-community version, we need to test all mysql linked software against mariadb. So first enable a long (I suspect very long) list of those software. Perhaps there's a hook somewhere in obs, able to auto-build those deps.
Then test carefully, one by one, to be sure there's no big failure or regression with mariadb. and notice any changes or optimization needed to be applied by admins (db conversion etc) in a long readme.
Would be nice to have to support only one. But I've a doubt about the pure drop'in replacement. It's not like replacing cron by cronie ... There's user data involved in that case.
Hi Bruno,
If I would follow your steps, then that means that at one particular point in time we have "certified" that it works. What does that help? how does that help with any fast moving target like openSUSE Factory where things are constantly being updated, repackaged, etc?
I think focusing on what is maintainable is more important: What can be fixed easily when it has a problem? Can we get mariadb developers to priotize fixes for data loss or critical performance issues?
Can we get that for mysql community server? My guess is that for both the answer is "nay", which means that we can pick one over the other. I don't care which one, please just make the issue of maintaining a database (and "supporting" it in the sense of how opensuse is supported) more difficult by providing multiple flavors of it.
Thanks, Dirk
Sorry Dirk, away during a long and stress full week. I share your vision and feeling especially about the "nay" options :-( It's yes a question of resources to be able to maintain at least mysql-community-server & mariadb. I've the feeling that for not bothering too much our end users/admins we will have to keep the both at least for 12.1, no ? So more and more people can try mariadb as an alternative and give feedback about it. I especially (without knowing if mariadb has it inside) think about the awfull mix people can have now with mysql like tables in different engines format (archives, myisam, innodb, ndb) and the pain that can be to have a smooth upgrade/changes. After all you decide, (at least those who made have the power) :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Bruno Friedmann -
Cristian Rodríguez -
Dirk Müller -
Stefan Seyfried -
Wolfgang Rosenauer