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
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. 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? *** This bug has been marked as a duplicate of 58942 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |