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 11590667 for ecs-isp@2rosenthals.com; Fri, 27 Dec 2024 13:43:59 -0500 Received: from secmgr-va.randr ([192.168.200.201]:55536 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1tRFJO-000000002RO-1MFv for ecs-isp@2rosenthals.com; Fri, 27 Dec 2024 13:43:50 -0500 Received: from mta-101a.earthlink-vadesecure.net ([51.81.61.60]:51397) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1tRFJH-000000007UE-1kp1 for ecs-isp@2rosenthals.com; Fri, 27 Dec 2024 13:43:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; bh=nnmczmV2YnAC68sdpHmPwntPJ+JpmHXJM+GJz2 BYB9U=; 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=1735325023; x=1735929823; b=mnszk0vkuRYoh7s1cMJdsp0IJWe cwbnNA7Hw+f1yp7KOFml1NnBhMdf7FlnuY5fXEH9rKFFvsjjvi4TIXDmS6xjYhbFquFmnFR 3SlI1B9bmSUD1FLKdG3Ia6SZEVPKGnSW8mTb/UDC1TCRmngCw1J6qJR4ruJIMx5uIv3BfAh pXlhCc5pSJzuHtk2DoSbQa6ZT/IEniKctglCLMqE/3jHzAefyxIVBNJ7jzbZLs1How1IniH dqAfpZPwilxxP0dN1pnmhkElRLY9/MnH6uwmBucZXkCdXe8y8FwGY/7AY2gMqqdALX2kMuj tRLoLtazGEFOXSnzTVUwxowur44h2ZQ== Received: from slamain ([172.56.178.196]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id 293df4ab-18151ce9ffa20d27; Fri, 27 Dec 2024 18:43:43 +0000 Message-ID: <676eec28.24.mr2ice.fgrirsq@earthlink.net> Date: Fri, 27 Dec 2024 10:04:24 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] (clamav) freshclam and cron/2 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 12/27/24 at 05:08 PM, "Massimo S." said: Hi Massimo, >of course this is the first thing i tried, That may be true, but until now we could only guess that you actually tried this command. Unless you tell us, you are the only one that knows exactly what you did and did not do. >yum want to update also dependacy: dash-sh >doing that i got 2 errors: OK. This typically has a simple solution. >il file /@unixroot/usr/bin/sh dell'installazione di >dash-sh-0.5.10.2-1.oc00.pentium4 >entra in conflitto con il file del pacchetto ash-0.0.0-10.oc00.i386 You need to add a note to your yum cheat sheet reminding you to check the the package platform when conflicts occur. We have discussed this before. The i386 platform has been deprecated in favor of the pentium4 platform for quite a while and ask the error message you have switched /etc/rpm/platform to pentium4 but you still have some i386 packages installed. Yum will not automatically change platforms when you update a package for any number of good reasons. You need to force yum to do this when when you know it's what's needed. Try yum install ash.pentium4 and let's see if this is sufficient to resolve the conflicts. >even if i try to install dash-sh with a separate command (yum install >dash-sh) i get the same error Why would you expect otherwise? The solution is almost always going to be replace the package that triggered the confict not the package you cannot update because of the conflct. In this case, it's the ash package. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------