Bug 683533

Summary: [RFE] Indicate what packages will be obsoleted by "yum update" prior to performing the update
Product: Red Hat Enterprise Linux 6 Reporter: J.H.M. Dassen (Ray) <rdassen>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: adevolder, mkhusid, pknirsch, rbinkhor
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-02 16:52:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 607248, 756082    

Description J.H.M. Dassen (Ray) 2011-03-09 16:30:36 UTC 
2. What is the nature and description of the request?
	Customer would like 'yum update' to indicate obsoleted packages before confirmation
3. Why does the customer need this? (List the business requirements here)
	As an admin, we need to know such things are happening before we agree to the update
4. How would the customer like to achieve this? (List the functional requirements here)
	yum would check for obsolete packages, and inform the user that packages would be obsoleted before asking for confirmation
5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
	yum update a package that would induce obsoletes, and view the display before confirmation
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
	No
7. How quickly does this need resolved? (desired target release)
	RHEL 7
8. Does this request meet the RHEL Inclusion criteria (please review)
	Yes
9. List the affected packages
	yum
Comment 2 seth vidal 2011-03-09 16:51:49 UTC 
in rhel6 I'm pretty sure we're outputting all the pkgs being replaced via obsoletes before we confirm to run the transaction.

Can the customer provide the specific case they are seeing?
Comment 3 J.H.M. Dassen (Ray) 2011-03-09 17:25:28 UTC 
(In reply to comment #2)
> Can the customer provide the specific case they are seeing?

Changing NEEDINFO over to Allan Voss who owns the customer case.
Comment 4 Allie DeVolder 2011-03-21 16:37:20 UTC 
In most cases, he's seen the issue with locally-built packages. One that was provided by us that did this is the tzdata package.
Comment 5 James Antill 2011-03-21 19:11:03 UTC 
 Which tzdata pacakge? This is logged against RHEL-6, which has had two tzdata updates ... neither of which have obsoleted anything, AFAICS.