I know there've been attempts to make sure this works, and I don't know yet why it doesn't, but just filing a bug quickly with the result of my test.
I did a minimal install of F18, did 'yum install mysql-server', 'yum update', 'systemctl enable mysqld.service', rebooted, ensured I could do 'mysql -u root' and 'systemctl status mysqld.service' returned enabled and active, and then did a fedup upgrade to F19. I got mariadb-server-5.5.31-1.fc19 to replace mysql-server, but on boot of the newly upgraded system, 'systemctl status mariadb-server.service' returns 'disabled', and 'mysql -u root' does not work.
Nominating as a freeze exception issue: if we can fix this for upgrades that don't use the update repos, it'd be nice.
"'systemctl status mariadb-server.service' returns 'disabled'"
grr, I don't know why I typed that. I meant 'systemctl status mysqld.service' . The service file is present and the service works fine if enabled, but it is disabled after the upgrade.
An update mariadb-5.5.31-4.fc19 that should fix this issue is already in Bodhi. Can you verify it fixes the issue, Adam?
Since the build is already in testing, it means it should be 0-day update at worst. The question is -- do we need it to be in fedora 19 release repo?
If fedup uses updates repository, then 0-day update should work fine, right? It will only affect new installations from DVD without updates repository enabled, which actually doesn't matter, because this issue is valid only when upgrading.
So, I'm not sure if this really needs to be freeze exception. However, I'm not against it generally and I may also miss some scenario where we really need it.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mariadb-5.5.31-4.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mariadb-5.5.31-4.fc19 has been submitted as an update for Fedora 19.
Honza: fedup can at least theoretically do a media-based upgrade - it can use a DVD or DVD ISO as a source of packages. It is also possible that people may run an upgrade with the updates repo disabled if it proves to work around some other issue on upgrading. Neither is the end of the world, but it may be worth fixing.
Discussed at 2013-06-24 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-blocker-review-8.2013-06-24-16.00.log.txt . This was rejected as a freeze exception issue: it was considered that it'd be pretty unlikely for a system with an active MySQL server to do a non-network upgrade, and in any case the consequence is not too terrible. The fact that the maintainers managed to break installations with their first attempt to fix this didn't give us too much confidence that we should take their *second* attempt to fix it with only three days before go/no-go; we felt a lot more comfortable sticking with a build that we at least know does not catastrophically break anything.
mariadb-5.5.31-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.