Bug 151909

Summary:	upgrade from rh-postgresql to postgresql breaks system
Product:	Red Hat Enterprise Linux 4	Reporter:	Tuomo Soini <tis>
Component:	postgresql	Assignee:	Tom Lane <tgl>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	hhorak
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-23 16:06:49 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 Tuomo Soini 2005-03-23 14:26:10 UTC

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

Description of problem:
yum upgrade from rhel-3 rh-postgresql to rhel-4 postgresql fails because
wrong package obsoletes rh-postgresql-SUB_PACKAGE:s.

postgresql package obsoletes all rh-postgresql-* sub-packages while
postgresql-server should obsolete rh-postgresql-server.

Currently postgresql package has obsoletes for all sub-packages so update will remove all sub-packages leaving system without postgresql-server.

Version-Release number of selected component (if applicable):
postgresql-7.4.7--2.RHEL4.1

How reproducible:
Always

Steps to Reproduce:
1. have rhel-3
2. yum update to rhel-4
3. there is no postgresql-server package (or other postgresql-*) sub-packages.
  

Actual Results:  postgresql and postgresql-libs packages are installed on system. but all other sub-packages are missing.

Expected Results:  If rpm tag:

Obsoletes: rh-postgresql-server

was in correct sub-package, upgrade would have worked.

And same goes for other sub-packages.
postgresql-tcl should obsolete rh-postgresql-tcl etc.


Additional info:

Comment 1 Tom Lane 2005-03-23 16:06:49 UTC

A fix for this is pending for RHEL4 U1.

*** This bug has been marked as a duplicate of 144435 ***