Bug 54841 - Enigma FTP upgrade: no way to select packages when default set does not fit.
Summary: Enigma FTP upgrade: no way to select packages when default set does not fit.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-10-20 17:38 UTC by Aleksey Nogin
Modified: 2007-04-18 16:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:48:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Aleksey Nogin 2001-10-20 17:38:30 UTC
If during an FTP upgrade I choose not to customize the set of packages to
be installed and it later turns out that the default set would not fit on
one of the filesystems, there is no way to go back and specify that I now
want to have a smaller set of packages installed. I can go back a few steps
but I hit the "can not unmount the filesystems" before I get to the menu
that asks whether i would like to customize the set of packages.

P.S. This bug together with bug 54840 (no way to abort the upgrade)
basically means that the upgrade is completely stuck with no chance to

Comment 1 Brent Fox 2001-10-24 03:34:18 UTC
Yes, there are currently some limitations with upgrading.  Basically, if you are
upgrading a system that doesn't have much free space left, it's possible to get
in the situation that you hit.  katzj and msf, anything we can do here?

Comment 2 Brent Fox 2001-10-24 03:36:01 UTC
*** Bug 54840 has been marked as a duplicate of this bug. ***

Comment 3 Michael Fulbright 2002-03-26 17:43:59 UTC
Deferring to future release.

Comment 4 Red Hat Bugzilla 2006-02-21 18:48:12 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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