Bug 167120
Summary: | up2date attempts to install package that is already installed (javamail), and generates an error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | chris suttles <suttles> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | Beth Nackashi <bnackash> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHBA-2006-0105 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-15 15:33:58 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: | |||
Bug Depends On: | |||
Bug Blocks: | 168424, 169775 |
Description
chris suttles
2005-08-30 16:12:32 UTC
Hmm, interesting. javamail obsoletes javamail-monolithic. Why they are then in the same channel is a good question. up2date will always attempt to replace javamail-monolithic with javamail, so the packaging here seems a bit bogus. Since it seems the packages don't actually obsolete as much as they conflict (aka, both shouldn't be installed at the same time) javamail should have a conflict on javamail-obsolete. I'm also not sure I understand the reasoning for having a set of packages, and then a single package that encompasses everything from multiple packages. There is a up2date bug, however, in that it's not properly detecting that an available obsoleting package is already installed (though, that in itself implys that the system has both a package installed, and a package that obsoletes it, which is kind of off kilter to begin with). However, a similar bug to this was fixed with the update 4.4 for rhel3 in U2, so this should be resolved with the rhel3u2 update. Can the customer duplicate this with the currrent U3 up2date? looks to be a packaging bug, so closing An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0105.html |