Ubuntu
mysql-dfsg-5.1 package

package mysql-client-core-5.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/mysql', which is also in package mysql-cluster-client-5.1 0:7.0.9-1ubuntu7

Bug #668177 reported by Sven on 2010-10-29

This bug report is a duplicate of: Bug #577041: package mysql-cluster-client-5.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/mysql', which is also in package mysql-client-core-5.1 0:5.1.41-3ubuntu12. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mysql-dfsg-5.1 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Happened during Synaptic install

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: mysql-client-core-5.1 (not installed)
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic-pae i686
Architecture: i386
Date: Thu Oct 28 21:43:52 2010
ErrorMessage: trying to overwrite '/usr/bin/mysql', which is also in package mysql-cluster-client-5.1 0:7.0.9-1ubuntu7
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: mysql-dfsg-5.1
Title: package mysql-client-core-5.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/mysql', which is also in package mysql-cluster-client-5.1 0:7.0.9-1ubuntu7

Tags:

Revision history for this message

Sven (sprevrha) wrote on 2010-10-29:

AptOrdering.txt Edit (7.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (534 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (69.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (101.5 KiB, text/plain; charset="utf-8")

Revision history for this message

James Page (james-page) wrote on 2010-11-04:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 577041, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.