Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 73139

Summary:	gnome-libs conflicts with db1
Product:	[Retired] Red Hat Linux	Reporter:	Jim Radford <radford>
Component:	gnome-libs	Assignee:	Havoc Pennington <hp>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	katzj, notting
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:	2006-02-21 18:49:32 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 Jim Radford 2002-08-31 02:12:24 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020820

Description of problem:
both db1-1.85-8 and gnome-libs-1.4.1.2.90-20 both contain

 /usr/bin/db1_dump185
 /usr/lib/libdb1.so.2
 /usr/lib/libdb1.a

Either gnome-libs probably shouldn't provide these files since if you  obsolete
db1 then you can't have db1-devel installed.

Comment 1 Havoc Pennington 2002-09-04 18:53:27 UTC

See explanation on #73138 - do we need an explicit Conflicts? The fact that the
files conflict should be enough right... 

db1-devel isn't intended to be installable; the point of moving db1 into
gnome-libs was to kill any compilation vs. db1.

Comment 2 Jim Radford 2002-09-04 21:27:19 UTC

I think adding an explicit conflict is the least that should be done.  Just
leaving conflicting files seems rude.  Do I have to crosscheck every file from
every package just to decide what to install?  Why not just leave db1 as a
separate package?  Clearly it is required by gnome-libs otherwise it wouldn't be
there.  Why hide that fact?

Comment 3 Havoc Pennington 2003-01-07 21:39:19 UTC


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

Comment 4 Red Hat Bugzilla 2006-02-21 18:49:32 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.