Bug 4855

Summary:	Upgrade installation errors
Product:	[Retired] Red Hat Linux	Reporter:	nathan.zook
Component:	installer	Assignee:	Matt Wilson <msw>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-09-08 16:31:05 UTC	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 nathan.zook 1999-09-02 15:00:41 UTC

Upgrade installation is far too limited.  In particular,
the bash2 package did not upgrade bash.  Also, the lilo
"upgrade" executed as a straight install, which overwrote
the old lilo executable.  (5.2->6.0)  The casual user is
not likely to catch these things. This is without
attempting a full audit.<BR>

In general, during an upgrade, I would like to see options
for "packages not previously available", "packages now part
of default" and the like.

Comment 1 Preston Brown 1999-09-02 18:50:59 UTC

bash2 didn't replace bash, it coexists beside bash1.

the installation suggestions will be addressed at some future point in
time.

Comment 2 Jeff Johnson 1999-09-08 16:31:59 UTC

I'm preserving this bug by reolving to REMIND and changing the
component to installer.

Comment 3 openshift-github-bot 2015-09-30 19:42:50 UTC

Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/993233d1919089b59b9af5fa818b5f4f6b8c07f0
Issue 4855 - warning flickers about build config and deployment config not existing