On 04/05/10 23:47, David C. Rankin wrote:
I did an update yesterday and with zypper's or yast's 'magic' the 'update' deleted mysql from my system and replaced it with 'MariaDB'. I sure in the heck didn't tell it to do that. Somebody at Novell included code somewhere that says "On the next update, delete mysql and replace it with MariaDB -- and don't make it obvious to the user."
I do have OBS-database as a repository and looking at the individual repos, that is where 'sweet Maria' must have come from. I think you are safe as long as you don't have the database repo active. (Of course, I could be wrong there - you might meet her on your next date .. I mean update ;-)
That was slightly inflammatory ... You are using an OBS repository. Not inherently bad, but don't use 'em mindlessly - and certainly don't claim that what you got from there is a "system update" - cause its not, it may not even be from Novell/SUSE, and you chose it. You didn't read the package list from the zypper up. Hence, its entirely your own fault if you don't notice what happens to your system. Noone at anywhere said "don't make it obvious to the user". The secret code that decides to install packages is called ... wait for it ... RPM! And believe it or not, it doesn't operate on Novell's (or MS, or Linus, or Stallman) instructions. Its workings are entirely transparent. Don't try shifting the blame to SUSE by pointing at zypper or Yast. They're just frontends. What (I am guessing) happened is that someone created a new mariadb package in OBS:server:database. This is completely reasonable, as it is interesting new software. In the spec file they wrote "Provides: mysql = %{version} Obsoletes: mysql < %{version}" which is sort-of true, you certainly don't want both installed at the same time, and mariadb does provide everything that mysql did. At this point it is literally a complete copy as far as I can tell. RPM then had a look at this package and said look! A new package that obsoletes one I've got installed! Let's update! And unfortunately you didn't read when it told you it was going to do this so it went ahead. In fact looking at the mariadb specfile, what I described above is exactly what happened. I doubt the author of the mariadb package wanted to force everyone to switch to mariadb. The simple fix is to no longer have mariadb "Obsolete: mysql" but simply "Conflict: mysql". 2 minutes work. Everyone, no need to go crazy assigning blame over a trivial error. There is no evidence that anyone has any hidden agenda, and *no evidence that the default in Factory or future released versions is going to change*. mariadb isn't even in Factory. Someone packaged mariadb in a side project is all. News at 11. Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org