Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 139019 - System upgrade appears to ignore deps on rpms that are already installed
Summary: System upgrade appears to ignore deps on rpms that are already installed
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 3
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-12 15:33 UTC by Steve Hill
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-11-12 15:43:25 UTC
Type: ---

Attachments (Terms of Use)

Description Steve Hill 2004-11-12 15:33:42 UTC
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  Upgrading to Fedora Core 3 causes the (now obsolete) 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 15:43:25 UTC
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.