Bug 151498

Summary:	up2date could protect core packages from being replaced
Product:	Red Hat Enterprise Linux 4	Reporter:	Dag Wieers <dag>
Component:	up2date	Assignee:	Pradeep Kilambi <pkilambi>
Status:	CLOSED WONTFIX	QA Contact:	Ken Reilly <kreilly>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	k.georgiou, redhat, tsanders
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:32:46 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:
Bug Depends On:
Bug Blocks:	151519

Description Dag Wieers 2005-03-18 17:52:01 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Galeon/1.3.20

Description of problem:
I guess it would benefit everyone (Red Hat, users, me) if up2date had an option (maybe enabled by default) to protect it's own/core packages. Ie. prefer RHN packages over 3rd party packages.

I guess it would make sense to have this by default since it could prevent support calls to Red Hat about something that is caused by 3rd party packages.

I try to keep the number of replaced packages down, but a switch like this could allow me to offer more packages and leave it up to the user whether to use the official package or the 3rd party package.

This in itself will lead to a better understanding what packages are not Red Hat's (and by consequence excluded from support).

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


How reproducible:
Always

Steps to Reproduce:
1. RFE
2.
3.
  

Additional info:

Comment 1 Dag Wieers 2005-03-18 17:54:19 UTC

*** Bug 151499 has been marked as a duplicate of this bug. ***

Comment 2 Suzanne Hillman 2005-03-18 21:31:13 UTC

Internal RFE bug #151519 entered; will be considered for future releases.

Comment 4 Jiri Pallich 2012-06-20 13:32:46 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.