Bug 24682 - Duplicate versions of MySQL after upgrade.
Summary: Duplicate versions of MySQL after upgrade.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.0
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-23 10:28 UTC by lasse
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-01-25 01:42:17 UTC
Embargoed:

Attachments (Terms of Use)

Description lasse 2001-01-23 10:28:06 UTC 
I tried to update mysql (MySQL) with the up2date tool. with the following
command:

 up2date mysql mysql-devel mysql-server

The result was:

 file /usr/bin/isamchk from install of mysql-3.23.29-1 conflicts with file
from package MySQL-3.23.28-1
file /usr/bin/isamlog from install of mysql-3.23.29-1 conflicts with file
from package MySQL-3.23.28-1
file /usr/bin/my_print_defaults from install of mysql-3.23.29-1 conflicts
with file from package MySQL-3.23.28-1

etc.. for all the packages:


However, the update went through and I've now ended up with:

 rpm -q mysql
  mysql-3.23.22-6
 rpm -q MySQL
  MySQL-3.23.28-1

The server is a RH6.2 uppgraded to RH7.0.
Comment 1 lasse 2001-01-23 10:32:24 UTC 
On further inspection it seems that the problem is not related to up2date but
rather on
the RedHat upgrade procedure.
Comment 2 Nalin Dahyabhai 2001-01-25 01:42:13 UTC 
What is the output of "rpm -qi MySQL"?
Comment 3 Nalin Dahyabhai 2001-01-25 01:48:41 UTC 
Package names are case-sensitive, and I suspect that the MySQL
packages are not the ones we shipped.  Changing the mysql package's
name to MySQL would break upgrades.
Note You need to log in before you can comment on or make changes to this bug.