In <list-4790015@2rosenthals.com>, on 11/06/26
at 09:47 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi all,
I am going to remain vision challenged for the next week or so, so I've
been a bit offline and my replies may remain a bit slow.
>But i've seen that my issue is python on platform i686,
>due for an old installation of the yum/rpm stack.
>All the rest (yum, rpm, libc etc. etc.) is not updated to
>the latest builds on pentium4 platform.
>But i'm not able to migrate python from i686 to p4.
I have a similar problem/project - leftover i686 packages that yum refuses
to update. Fortunately, none of these packages are preventing updates
that I really want to happen. I started to work out a solution but since
this was more a want than a need, the project got put aside.
The current state of my solution, which is not yet tested is
rpm -Uvh --nodeps --force -p yourpackage.rpm
-U update
-v, --verbose Verbose operation
-h, --hash print hash marks as package installs (good with
-v)
--nodeps don't verify package dependencies
--force short hand for --replacepkgs --replacefiles
-p, --package query/verify a package file (aka .rpm)
What this should do is replace the existing i686 files with the pentium4
versions. As long as both the i686 and the pentium4 rpms contain the same
set of files, this should work as expected, as long a rpm is willing to
replace the files.
When I get back to this project and I have proper backups, we shall learn
if this does the expected.
FWIW, I used yum shell to do a number of these conversions. Unfortunately
yum shell broke for me in v3.4.3. I'll know if the latest yum fixes this
when I get back to this project.
When it works, yum shell is the easiest solution. It handles the
dependency checks in a way that avoids the platform change conflicts.
back to list