Bug 39884
Summary: | up2date cannot handle multiple versions of the same package | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Stephen Tweedie <sct> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-28 15:38:18 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: |
Description
Stephen Tweedie
2001-05-09 15:39:09 UTC
looks like the computation to figure out which of the installed packages is newer isnt considering epoch, but the code to determine if a package needs an update is using it. The packages question are: libxml-2.0.0-1-i386 (no epoch) libxml-1.8.10-1.i386 (epoch of 1) So up2date thinks libxml-2 is the newest installed, but that libxml-1.8 is "newer", and trying to install it. working on a fix... Is this a crufty bug? Can it be retired? yeah, crufty bug, long since fixed. |