Bug 102522
Summary: | update of already installed package | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Michael Redinger <michael.redinger> | ||||||
Component: | up2date | Assignee: | Bret McMillan <bretm> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.0 | CC: | bernd.bartmann, jqpublic-rhn, shillman | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-10-19 19:35:28 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Michael Redinger
2003-08-16 14:12:30 UTC
I should add that I have additional RPMs (for example all the "missing" *-devel packages) installed. This should not matter, just thought I should mention it ... *** Bug 103156 has been marked as a duplicate of this bug. *** On the same machine (bash is still listed in up2date ...), updated to Beta 2 (up2date-3.9.12-1), I now have the same problem with redhat-config-securitylevel (1.2.4-1). Created attachment 109491 [details]
up2date -u output
Another person who had problems similar to this determined that somehow multiple versions of the same rpm were installed, causing this problem. Can you check if there are multiple via rpm -q on the package name? If there are multiple, and you are not on a system with multilib (ie, x86_64 can have both x86_64 and i386 packages), it's possible that at some point an update or install of rpms didn't finish, so they were both left there. Because it's possible the newer one didn't actually finish installing (based on the likely reason that the two versions are there), I'd remove that one, and try the update again. I am having a similar problem when attempting to up2date a fresh install of RHEL3/i386 update 6. The conflict happens with the openoffice.org-1.1.2-28.2.0.EL3 package. That exact package is on the update 6 CD's, but up2date still tries to upgrade it, which fails. I went through the redhat-users and bugzilla archives and I saw that others have seen this problem with an earlier update on x86_64, but my problem is happening with the vanilla i386 update 6 release. The solution presented in RHBA-2005:650 does not work for me since the rpm presented there is identical to the one on the ISO's right down to the md5's. Here is some output: [root@localhost root]# rpm -q openoffice.org openoffice.org-1.1.2-28.2.0.EL3 [root@localhost root]# rpm -q --obsoletes openoffice.org-1.1.2-28.2.0.EL3 openoffice openoffice.org-style-gnome [root@localhost root]# rpm -q --qf "%{name}-%{version}-${release}.${arch}\n" openoffice.org openoffice.org-1.1.2-28.2.0.EL3.i386 [root@localhost root]# rpm -q rpm rpm-4.2.3-24_nonptl [root@localhost root]# rpm -q up2date up2date-4.4.44-3 Steps to reproduce: 1) install RHEL3 ES update 6 using the "everything" selector from the ISO's on rhn.redhat.com 2) after the install reboot, register the server, and run up2date -u Please let me know if you need any more information to debug this problem. Thanks much. Created attachment 123755 [details]
i386 up2date -u output
Is this still an open bug? Trying to work out these as well as other up2date issues This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |