I have been using my own builds of mysql 4.1 on a number of linux systemslately. Might I suggest using the rpm tool to remove the mysql (3.x) package and then install your hand-built 4.1? This will take mysql out of the package database altogether and prevent the updater from dealing with it. The same goes for PHP which will not be able to connect to a 4.x mysql server with it's build-in 3.23 client. On Sat, 2004-07-24 at 14:55, Kenneth Porter wrote: > --On Saturday, July 24, 2004 9:12 AM -0500 Jason L Tibbitts III > <tibbs@xxxxxxxxxxx> wrote: > > > Just a note that if you are running a self-compiled mysql4 (perhaps > > made using the instructions on fedoranews) then last night's PHP > > update will hose your system. For me, the dependency resolution > > deleted mysql-server and installed the old mysql3 "mysql" package. To > > fix, grab the PHP SRPM, rebuild it against your mysql4 libraries and > > install it without letting the automatic updater get to it. > > Did you install MySQL4 as an RPM? Or did you just compile the tarball and > copy the files into place (perhaps with "make install")? The MySQL sources > should be set up to build RPM's, so I recommend using rpmbuild as a mortal > to do so. -- - michael dykman - michael@xxxxxxxxxxx
