Bug 784524 - Remove ctdb as it depends on conflicting tdb-tools
Summary: Remove ctdb as it depends on conflicting tdb-tools
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: comps
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Kopecek
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 09:23 UTC by Tomas Kopecek
Modified: 2012-02-21 05:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 05:57:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0315 0 normal SHIPPED_LIVE redhat-release enhancement update 2012-02-20 19:19:10 UTC

Description Tomas Kopecek 2012-01-25 09:23:19 UTC 
New patch in ctdb added require for tdb-tools which is conflicting with default installation. It should be fixed on tdb-tools level https://bugzilla.redhat.com/show_bug.cgi?id=736112 , but there is not enough time to fix it for RHEL 5.8 RC. 
So possibility is to remove ctdb from ClusterStorage comps and add it to @conflicts group.

Steps:
1) 5.8 (this bug)
  a) remove ctdb from comps (cluster-storage group)
  b) add ctdb to @conflicts
2) 5.9 
  a) fix tdb-tools
  b) remove tdb-tools from @conflicts
  c) return ctdb to comps
Comment 1 Tomas Kopecek 2012-01-25 09:24:31 UTC 
Related: https://bugzilla.redhat.com/show_bug.cgi?id=765887
Comment 4 errata-xmlrpc 2012-02-21 05:57:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0315.html
Note You need to log in before you can comment on or make changes to this bug.