Bug 152854

Summary:	Yum updates for Red Hat 7.3 are inconsistent
Product:	[Retired] Fedora Legacy	Reporter:	David Lawrence <dkl>
Component:	General	Assignee:	Fedora Legacy Bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified
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:		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 David Lawrence 2005-03-30 23:29:47 UTC

After a fresh installation of Red Hat Linux 7.3 on an Intel P4 platform, I
installed yum from download.fedoralegacy.org and tried to do a "yum update".  I
received the messages:

.... identical dependency loop exceeded.
package mozilla-psm needs mozilla-nss = 1.0.2-2.7.3 (not provided)
package mozilla-psm needs mozilla-nss = 1.0.2-2.7.3 (not provided)

I have been doing a fair number of Red Hat 7.3 installations over the past
several weeks, and the yum updates used to work.  As I recall, they stopped
working (and started displaying the above problem) somewhere around November 5.

Here is what uname -v -r reports for my system:

2.4.18-3smp #1 SMP Thu Apr 18 (etc.)

I would appreciate any help with this problem.



------- Additional Comments From rccall 2004-11-19 11:29:57 ----

I have since discovered that "yum upgrade" (as opposed to upDATE) will apply the
necessary updates to my system.

Other possible work-arounds (e.g., removing mozilla-nss before running update)
were also suggested on the fedoralegacy discussion group; but I did not try them.



------- Bug moved to this database by dkl 2005-03-30 18:29 -------

This bug previously known as bug 2286 at https://bugzilla.fedora.us/
https://bugzilla.fedora.us/show_bug.cgi?id=2286
Originally filed under the Fedora Legacy product and General component.

Unknown priority P1. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, dkl.
   Previous reporter was rccall.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.