Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 139019 - System upgrade appears to ignore deps on rpms that are already installed
System upgrade appears to ignore deps on rpms that are already installed
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-11-12 10:33 EST by Steve Hill
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-12 10:43:25 EST
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 Steve Hill 2004-11-12 10:33:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020

Description of problem:
When upgrading, Anaconda seems to ignore the dependencies of RPMs that
are not part of the standard installation.

e.g. I have the "multisync" RPM installed under Fedora Core 2, whcih
is not part of the standard distribution.  Multisync is dependent on
libldap.so.2.  Upgrading to Fedora Core 3 causes the (now obsolete)
libldap.so.2 library to be removed without warning, rendering
multisync inoperable.

Version-Release number of selected component (if applicable):
Fedora Core 3

How reproducible:
Didn't try

Steps to Reproduce:
1. Install non-standard packages onto a FC2 system which have
dependencies that are satisfied under FC2 but not FC3
2. Upgrade to FC3

Actual Results:  No warnings during installation, dependencies were
just removed.  Programs that depended on removed libs then would not

Expected Results:  1. Anaconda should attempt to satisfy the
dependencies if possible
2. A warning should be displayed, informing the user of which packages
will have broken dependencies after upgrade

Additional info:
Comment 1 Jeremy Katz 2004-11-12 10:43:25 EST
We try to satisfy them if possible, but in many cases (such as this),
they're not.  One of the steps that must be done after an upgrade is
ensuring that all third party software you previously had installed
still functions or gets rebuilt/upgraded as needed.

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