http://bugzilla.novell.com/show_bug.cgi?id=586082
http://bugzilla.novell.com/show_bug.cgi?id=586082#c4
--- Comment #4 from Aaron Bockover 2010-03-07 18:59:52 UTC ---
Playing around with different scenarios, I notice that if I just do "zypper in
-f mysql" to reinstall the package, I end up with two new databases in
/var/lib/mysql:
/abockwordpress@002efinal@002dbackup
/abockwordpress@002ebackup
(where abockwordpress is the working/original DB)
More interesting is that after reinstalling the one package, I do end up with a
/var/log/mysql/mysqld-upgrade.log (which contains innocuous data).
Next, I tried "zypper remove mysql" (after restoring /var/lib/mysql from the
pre "in -f" test copy). This worked cleanly and didn't affect /var/lib/mysql at
all. It did not attempt to verify the integrity/compatibility of any of the
databases unlike reinstalling with "in -f".
Finally, I tried both scenarios again (in -f, remove/in) with the
/var/lib/mysql/mysql_upgrade_info file removed.
With "in -f " in this case, no attempt is made to check the databases as in the
uninstall/install case. Same for the uninstall/install case.
So far to me this seems like it may just be a dist upgrade issue.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.