Bug 152854 - Yum updates for Red Hat 7.3 are inconsistent
Yum updates for Red Hat 7.3 are inconsistent
Product: Fedora Legacy
Classification: Retired
Component: General (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Fedora Legacy Bugs
Depends On:
  Show dependency treegraph
Reported: 2004-11-17 11:38 EST by David Lawrence
Modified: 2008-05-01 11:38 EDT (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description David Lawrence 2005-03-30 18:29:47 EST
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@optonline.net 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@redhat.com 2005-03-30 18:29 -------

This bug previously known as bug 2286 at https://bugzilla.fedora.us/
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@redhat.com.
   Previous reporter was rccall@optonline.net.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

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