On Tue, 6 May 2008, Gordon Hay wrote:

> > I upgraded my server from Fedora FC6 to FC8, and all seemed OK at
the
> > end of the process.  DBMAIL (2.2.10) continues to work as expected.
But
> > a subsequent "yum update" to catch all the post-FC8 updates threw up
a
> > number of errors like this:
> >
> >                file /usr/bin/msql2mysql from install of
> >                mysql-5.0.45-6.fc8.x86_64 conflicts with file from
> >                package
> >        mysql-5.0.27-1.fc6.i386
> > 
> > Apparently there are conflicts between the FC8 64-bit packages and
the
> > FC6 32-bit packages.
> > 
> > How can I get past this?
> > I've asked on the Fedora list, but with no luck yet...
> > 
> > I'm reluctant to simply "yum remove" the old MYSQL then "yum
install"
> > the new one, in case my DBMAIL database get lost in the process...
> 
> So back it up first.
> 
> > Are there MYSQL experts here who can advise?
> 
> Mixing 32-bit and 64-bit packages is ill advised at best. Since you
just 
> upgraded the distro and are using FC, I am assuming that this is not
a 
> production system. If you are concerned about losing the DB, back it
up first, 
> but traditionally, removing the mysql package doesn't result in 
> /var/lib/mysql/* getting dropped.
> 
> Actually, re-reading what you wrote - are you saying you just upgraded
the 
> mysql package, not the whole distro? That's just asking for trouble. 
> Considering you weren't running the 64-bit version before, is your
actual 
> installed distro 64-bit? If it isn't, just slapping on a 64-bit
package won't 
> work - you'll need 64-bit kernel, glibc, and probably a few hundred MB
of other 
> 64-bit libraries before that'll have even a remote chance of working.
> 
> Gordan
> 

Sorry if I wasn't clear: I upgraded the whole FC6 system to FC8, and it
was 64-bit from the start, so I'm not trying to migrate from 32-bit
MYSQL to 64-bit MYSQL  (Lots of 64-bit packages seem to require that
their 32-bit counterparts are also installed.) 

My question still is: can MYSQL experts recommend the best way to remove
these conflicts with minimum risk to my DBMAIL system?  I'm not
experienced with MYSQL, so the more detailed your instructions, the
better my chances of doing it right...

Again, thanks in advance for any help.  



_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to