Bug 151363

Summary:	Custom install: openssh is not optional
Product:	[Fedora] Fedora	Reporter:	Indrek Kruusa <indrek.kruusa>
Component:	comps	Assignee:	Elliot Lee <sopwith>
Status:	CLOSED CANTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	4
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:	2007-01-13 20:14:08 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 Indrek Kruusa 2005-03-17 10:27:29 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Description of problem:
openssh will be installed even when I unselect all software options in Custom install screen.

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


How reproducible:
Always

Steps to Reproduce:
1. start install from CD no. 1
2. choose Custom install
3. unselect all software options

Additional info:

Comment 1 Elliot Lee 2005-03-22 03:47:45 UTC

Same deal as with cups :)

Comment 2 John Thacker 2007-01-13 20:14:08 UTC

(This is a mass update of bugs which have been in the NEEDINFO state unmodified
for over a year and have not been confirmed for a still supported version of
Fedora Core.)

Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.

Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only.  Please install a still supported version and retest.  If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version.  Otherwise, if this a security issue, please change the
product to Fedora Legacy.  Thanks, and we are sorry that we did not
get to this bug earlier.