Bug 76144

Summary:	the new obsoletes functionality introduces unexpected side effects
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <aander07>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.0	CC:	gafton, mihai.ibanescu, srevivo
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:	2003-06-23 16:46:44 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:	77359

Description Need Real Name 2002-10-17 15:08:22 UTC

Description of Problem:

With the new obsoletes functionality, the expected behavior of up2date has
changed in a way that was suprising, and could be problematic.

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

up2date-2.7.61-7.x.1

How Reproducible:

100%

Steps to Reproduce:
1. Install a 7.0 machine with LPRng
2. run the initial up2date -- note that cups is not offered
3. run another up2date with the new client -- note that cups is now offered

Actual Results:

with the 2.7.61-7.x.1 up2date, it tries to upgrade LPRng -> cups

Expected Results:

the previous behavior where LPRng was kept at errata release levels

Comment 1 Adrian Likins 2002-10-18 21:04:35 UTC

working on some server side fixes for this...

basically get to blacklist random packages from 6.2-7.3 with bogus
useage of Obsoletes.

Comment 2 Adrian Likins 2002-12-06 22:12:47 UTC

the server side changes, and the new obsoletes blacklist support 
should take care of this. Moving to modified.

Comment 3 Need Real Name 2003-06-23 16:46:44 UTC

The given test case works, and I'm going to assume that all instances of this
issue have been fixed.