Maybe there is something wrong with the mysql_update program, since
Marcin got
mysql_upgrade: [ERROR] 1813: Tablespace '`mysql`.`innodb_table_stats`'
exists.
and I got
mysql_upgrade: [ERROR] 1007: Can't create database 'performance_schema';
database exists
@Marcin does manually running
I am unable to reproduce this error further.
This happened twice on separate VMs when upgrading to 16.04 from clean
installs of 14.04.4.
It has stopped happening on further upgrade attempts, so I would tend to
think that it has been fixed, maybe as a side effect of some other
update?
--
You
** 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
Public bug reported:
Upgrading from 14.04 to 16.04, installer reported this bug.
Just need to access the uploaded logs to see if the issue is the same as
#1567884
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu
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
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 also am running into this bug on the i386 10.04 RC. The fix appears to
work for me too.
--
checkbox does not report backend failures; backend spins out of control
https://bugs.launchpad.net/bugs/563588
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And by fix I mean remove the test-curus-sasl2.py references. Though this
is probably a hacky fix.
--
checkbox does not report backend failures; backend spins out of control
https://bugs.launchpad.net/bugs/563588
You received this bug notification because you are a member of Ubuntu
Bugs, which is
10 matches
Mail list logo
