[TriLUG] Fedora Core 2 + MySQL 4.1
David A. Cafaro
dac at trilug.org
Wed Sep 22 23:42:26 EDT 2004
I know this may sound like a stupid question, but have you just tried
building the MySQL src rpm's for your system then doing an "rpm -Uvh
mysql*.rpm" on the newly built rpms?
In the past on fc2 (and fc1, redhat 9, RHEL3, etc) I was able to just
download the rpm's from MySQL (the binary ones) and do an "rpm -Uvh
mysql*.rpm" on them. Usualy that would fail with something about
openssl dependencies failing. Adding the --nodeps flag will allow for
the install, and no failures (the openssl ones are not show stopper
errors, just annoying if you compile/link things off them later).
I eventually changed to building from the source rpms ( "rpmbuild
--rebuild mysql*.src.rpm" ) to avoid this openssl errors.
-David
On Wed, 2004-09-22 at 18:55, Brian Henning wrote:
> Hi All,
> Some of you will recognize this as the issue I was winning the
> talking-to-self award in the IRC channel for today.. Well, I still haven't
> solved it. The low-down is:
>
> If I install the RPMs from mysql.com for 4.1, things get fubar'd (as someone
> correctly forewarned me). Dependencies get broken, and useful little things
> like being able to start mysql cease functioning.
>
> So could someone point me to a howto or discussion or whatever that would
> shed some good light on the right way to upgrade? I need to make sure that
> things like Perl-DBD-MySQL, php-mysql, etc. remain unbroken, because I make
> considerable use of them. I want to upgrade because I want to be able to
> use subqueries, which aren't supported before 4.1.
>
> TIA,
> ~Brian
--
David A. Cafaro
dac(at)trilug.org
Admin to User: "You did what!?!?!"
More information about the TriLUG
mailing list