You've got 3 options:<br><br>1) Remove MySQL 4.1 (i'm guessing you're on a RedHat distribution given the file places, could be wrong). You can use RPM directly to try to uninstall MySQL and all it's dependent packages or you can try going into xwindows and to the package manager there (add-remove programs if you're in a recent version of gnome) and remove MySQL from there.
<br><br>2) Try Upgrading MySQL 4.1 to 5.X in place using RPM, Yum, etc. I don't have a whole lot of experience here, but technically if you have all the packages you need in the same directory when you do the upgrade the RPM system SHOULD be able to figure out a way around it's dependencies to get everything installed. With some packages (don't know about MySQL) typically you're reduced to upgrading half your operating system to get it to work in this way. You might try to simply yum install the MySQL5 package and see what happens, who knows, this might be the easiest.
<br><br>3) Work "around" the currently installed MySQL. Doing this requires you to do a few things:<br><br>* use chkconfig to remove mysqld from the boot up process (optional, see steps at end for modifying mysqld to start your new MySQL istallation at boot, if you wish to do so then don't do this.)
<br>* Install the New MySQL version into a new place (I like /opt as it contains all the packages you've upgraded and /usr/local just gets CROUDED with crap), using either binaries or a code distribution (i've used both, both arn't too terribly difficult to put in place).
<br>* **IMPORTANT** add </installdirectory/bin> (e.g. /opt/mysql5/bin) to your PATH BEFORE any of the standard binaries paths (/usr/bin, /bin, /sbin, /usr/sbin, etc.)<br>* Modify your mysqld file in /etc/init.d (or whatever bootup file you're using to start safe_mysqld) to point to the new safe_mysqld binary.
<br><br>What all of this should do is to put the MySQL 5 installation AHEAD of the MySQL 4.1 installation. Any time you run a MySQL command (mysql, mysqladmin, safe_mysqld, etc.) it should pick up the 5.x versions BEFORE the
4.x versions due to your path setting. <br><br>Can't tell you how many times i've done this on RedHat/Fedora/Mandrake/etc. systems that use package managers. It's just easier to work around the package managers than to try to work with them...when removing Samba starts complaining about dependencies in the base X Windows libraries, it's time you decide either to install the new version of Fedora to upgrade your samba (which is stupid) or start figuring out how you can "obsolete" the RPMs that were previously installed, the above is the trick to doing so. Typically I have an installation rule: If i'm not interested in updateing the package when the operating system maintainer (redhat, mandrake, debian, etc.) decides it should be updated, or if I feel i'll want to update it more frequently than the os maintainer (cause we all know debian and redhat do SUCH a good job of keeping their systems up to date with the most recent set of code...) I simply DO NOT install that package during system installation time, and I use
tar.gz's or binary distributions to keep the system up to date on my schedule.<br><br>GL to you, working with the package managers of Linux are much harder than you'd think it would be.<br><br>--Douglas Wagner<br><br><div>
<span class="gmail_quote">On 5/1/06, <b class="gmail_sendername">Tom Lichti</b> <<a href="mailto:tom@redpepperracing.com">tom@redpepperracing.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
R. G. Newbury wrote:<br>> Tom Lichti wrote:<br>><br>>> R. G. Newbury wrote:<br>>><br>>>> I ma having a senior moment day I think.<br>>>><br>>>> I want to upgrade to mysql 5.0 from
4.1. The installation instructions<br>>>> which come with the (binary-version) tar, just talk about un-'tar'ring<br>>>> the file in a chosen folder and then adding that folder to PATH.<br>>>><br>
>>> The existing installation has the executable mysql and mysqld(_safe)<br>>>> files in /usr/bin, and the libraries in /usr/lib..<br>>>> There does not appear to be a particular folder containing all of the
<br>>>> program parts.<br>>>><br>>>> Anyone out there been through this and have any understanding of what<br>>>> should be done.<br>>>><br>>>> Geoff<br>>>><br>
>>><br>>> Sounds like your original installation was done using an RPM (or DEB)<br>>> file. If so, I'd see if there are pre-packaged versions available.<br>>><br>>> Tom<br>>><br>>
<br>> The client installed from the rpm, with --force but the server fails<br>> with dependency issues.<br>><br>> [root@tor2 tar]# rpm -ivf --force ySQL-client-5.0.20a-0.glibc23.i386.rpm<br>> Preparing packages for installation...
<br>> MySQL-client-5.0.20a-0.glibc23<br>><br>><br>> [root@tor2 tar]# rpm -ivf --force ySQL-server-5.0.20a-0.glibc23.i386.rpm<br>> error: Failed dependencies:<br>> MySQL conflicts with mysql-4.1.16-1.FC4.1.i386
<br>> MySQL-server conflicts with mysql-server-4.1.16-1.FC4.1.i386<br>><br>> [root@tor2 tar]# rpm -U --force MySQL-server-5.0.20a-0.glibc23.i386.rpm<br>> error: Failed dependencies:<br>> libmysqlclient.so.14
is needed by (installed)<br>> mod_auth_mysql-2.6.1-4.i386<br>> libmysqlclient.so.14 is needed by (installed)<br>> perl-DBD-MySQL-2.9007-1.i386<br>> libmysqlclient.so.14 is needed by (installed)
<br>> php-mysql-5.0.4-10.5.i386<br>> libmysqlclient.so.14 is needed by (installed)<br>> qt-MySQL-3.3.5-11.4.fc4.kde.i386<br>> libmysqlclient_r.so.14 is needed by (installed)<br>> MySQL-python-1.2.0-1.i386
<br>><br>><br>Upgrade:<br>mod_auth_mysql<br>perl-DBD-MySQL<br>php-mysql<br>qt-MySQL<br>MySQL-python<br><br>at the same time as MySQL 5.<br><br>Tom<br>_______________________________________________<br>mythtv-users mailing list
<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div>
<br>