Had the same problem.
Successfully installed it in the end by manually downloading the 5.6 version
from thier site.
When installing it manually ubuntu automatically updated it to the 5.7 version
but this time it seems to work.
Probably will work bu installing manually the 5.7 version as
** Changed in: mysql-5.7 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
package mysql-server-5.7 5.7.11-0ubuntu6 failed to
Guess Launchpad was having issues temporarily. The report is now at
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1571764
However, I'm now less sure I know what's going on - I restored the VM
state to before I ran do-release-upgrade and ran the upgrade to Xenial
again, and this time
I had the upgrader send a bug report but I can't access it:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+filebug/84c4b874-0579-11e6-8ed4-d485646cd9a4
I'm not 100% sure if it's the same bug, but the title it suggested was
the same as this one.
--
You received this bug notification
Steps to recreate:
- Set up a 14.04.4 64-bit base system using Ubuntu ISO installer or using
Vagrant, get the ubuntu/trusty64 box.
- Upgrade to latest packages (aptitude update && aptitude safe-upgrade)
- Install mysql (aptitude install mysql-server-5.5)
- Upgrade to pre-release Xenial
@Roger
I can't reproduce this. I tried:
lxc launch ubuntu:trusty mysql-upgrade
Then inside the container:
apt-get update && apt-get -y dist-upgrade
apt-get -y install mysql-server # this installed 5.5
do-release-upgrade -d
After the upgrade, mysqld 5.7 is running.
Roger, are you sure you
I have been testing the Trusty to Xenial upgrade path, and can confirm
this happens when upgrading to Xenial and mysql 5.7 from a clean install
of Trusty with mysql 5.5.
I'm not formally trained in the "Debian way" but from my experience it
seems like the "correct" way to resolve this might be to
> I can try, but, shouldn't that be done by the package upgrade
automatically?
Packaging maintains any configuration file customisations by (Debian)
policy. It would be nice if we could detect and fix up a known set of
configuration directives, but this is particularly error-prone because
** Changed in: mysql-5.7 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade:
Solved the problem by removing
myisam-recover = BACKUP
and
key_buffer = 16M
from my.cnf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
"Could you check them and fix if necessary and retry?"
Am I supposed to remove them from the config or change them in some way?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
package
I can try, but, shouldn't that be done by the package upgrade automatically? or
at least offer me to inspect the changes in the file when it is going to be
replaced?
It's not serious that every user of mysql needs to do plumbing every time that
a new release is done.
--
You received this bug
Your /etc/mysql/my.cnf file seems to still have the removed options
(key_buffer) and (myisam_recovery).
Could you check them and fix if necessary and retry?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
14 matches
Mail list logo
