From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 4790907 for ecs-isp@2rosenthals.com; Fri, 06 Nov 2026 14:07:27 -0500 Received: from [192.168.200.201] (port=40989 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.98.2) (envelope-from ) id 1wOgmW-000000002Hg-1ixx for ecs-isp@2rosenthals.com; Sun, 17 May 2026 15:04:08 -0400 Received: from mta-202a.earthlink-vadesecure.net ([51.81.232.240]:39071) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wdXxK-0000000022f-0ePT for ecs-isp@2rosenthals.com; Sun, 28 Jun 2026 14:39:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=F5jRpa5ariOy9RA8A5sE3VbGDBrBIkPlK8xNan s+K+4=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1793992027; x=1794596827; b=rKpjxUIrz49eI3ECvRMWJqvKGR+ KKoWytOOroeUZdmvQ0bMFcG3Yvlqeg7yKIT4ct2D9cUbpoA0P+N/SgPwZejRz8ZtHXIHiVt MDlgeVIOYG2IZyPVLXkf3nYIMyG09IMLa+/GgxBpfC52PqN2Q72KKk4Q8FYHqI16/HzL8ye K5B/JKb7iQAmkZ70x8gyvgX/Xfn0MZsDHao6rNQgU+/fRDzZwGSCXO+WwtlkeGB6QADzgcc opSAXKC53M0U1qTKrEQALOBVA9k7r2DnGV/yGI1Sqfb6KBUqh9Ht9hS8HVL0ZAYKnvjt3JF MEoBguElt9zgJf/9q+63Xf2yAJleUDQ== Received: from slamain ([107.202.224.188]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id 5373d5b1-18e58a3e61f43624; Fri, 06 Nov 2026 19:07:07 +0000 Message-ID: <6aee207e.12.mr2ice.fgrirsq@earthlink.net> Date: Fri, 06 Nov 2026 10:46:22 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] [warp] ANPM-YUM-RPM troubles X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 11/06/26 at 09:47 AM, "Massimo S." 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. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------