Bug 8581 - Update Agent Can't Resolve Dependencies
Update Agent Can't Resolve Dependencies
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
: 9767 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-01-18 16:26 EST by Michael Hipp
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-28 14:55:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2000:138 high SHIPPED_LIVE New, enhanced Update Agent for Red Hat Linux 6.x, 7.0 available 2000-12-21 00:00:00 EST

  None (edit)
Description Michael Hipp 2000-01-18 16:26:36 EST
When attempting to download & install a number of the packages shown by Red
Hat Update Agent via the browser, the Up2date frequently reports that it
can't resolve dependencies.  Even with "Attempts" set to the max value
(10).  This happens in particular when attempting to download
"control-center", "gnome-core", and "gnome-libs".  I believe I have
installed the latest version of Up2date.  Any help?
Comment 1 Preston Brown 2000-01-19 10:34:59 EST
before the agent tells you it cannot resolve dependencies, which packages are in
the selection box?
Comment 2 Michael Hipp 2000-01-19 19:36:59 EST
I just tried it again.  I selected "control-center" which it listed in the box.
It then made 10 attempts to resolve dependencies and ultimately died with the
error "Unable to resolve dependencies ...".  Yesterday I had similar symptoms
when attempting to retrieve "gnome-core" or "gnome-libs".
Comment 3 Preston Brown 2000-02-28 14:55:59 EST
*** Bug 9767 has been marked as a duplicate of this bug. ***
Comment 4 Preston Brown 2000-12-21 14:24:23 EST
fixed by errata being released shortly.

Note You need to log in before you can comment on or make changes to this bug.