crossgrading RPM packages

I have an ES4 server that I would rather not rebuild that has the correct
glibc revision, just the wrong architecture revision (eg, i386 instead of
i686).

I have tried `rpm -ivh --replacepkgs glibc-2.3.4-2.i686.rpm` but, am met
with the error 'glibc < 2.3.4 conflicts with glibc-common-2.3.4-2.i386'.

I have tried the --nodeps flag, and return errors about conflicts with
another package (glibc-2.3.2-95.33).

I have also pondered removing the existing glibc package, but given the
number of things that rely on it, I'm a bit hesitant to do that, even while
in single-user.

is there an easy way to crossgrade the i386 packages to i686, or am I better
off upgrading (to i686) the packages in question from a later version of
ES4?

I have already performed an upgrade from ES3.x to ES4.0 in the hopes that it
would realise that the CPU was an i686 class, and apparently it didn't.

Joseph Millman wrote:

> I have an ES4 server that I would rather not rebuild that has the correct
> glibc revision, just the wrong architecture revision (eg, i386 instead of
> i686).
>
> I have tried `rpm -ivh --replacepkgs glibc-2.3.4-2.i686.rpm` but, am met
> with the error 'glibc < 2.3.4 conflicts with glibc-common-2.3.4-2.i386'.
>
> I have tried the --nodeps flag, and return errors about conflicts with
> another package (glibc-2.3.2-95.33).

Use the force switch (in this case) instead.

Remove the glibc-2.3.2-95.33 and install the compat-glibc-2.3.2-95.30
package in it's place.


--
"A personal computer is called a personal computer because it's yours,
Anything that runs on that computer, you should have control over."
Andrew Moss, Microsoft's senior director of technical policy, 2005