package mysql-server-5.7 5.7.12-0ubuntu1.1 failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
package mysql-server-5.7 5.7.12-0ubuntu1.1 can not upgrade
子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.12-0ubuntu1.1
ProcVersionSign
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
mysql-server: Install
mysql-server-5.7: Configure
mysql-server: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Sun Jun 26 19:08:43 2016
ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
InstallationDate: Installed on 2016-04-22 (65 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.12-0ubuntu1.1 failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.