Bug 689549 - Need cluster build deps for rebuilding gfs2-utils
Summary: Need cluster build deps for rebuilding gfs2-utils
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: releng
Version: 6.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Dennis Gregorovic
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 18:48 UTC by Nate Straz
Modified: 2011-05-02 18:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-02 18:48:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nate Straz 2011-03-21 18:48:48 UTC
Description of problem:

The gfs2-utils package is included in Workstation, Client, and ComputeNode variants.  To rebuild it we need to make sure corosynclib-devel and openaislib-devel are included in the optional repo.

openaislib-devel is not found on the stable systems for TPS at this time. corosynclib-devel is found, but I don't see it in the trees.

Version-Release number of selected component (if applicable):
cluster-3.0.12-39.el6

How reproducible:
100%

Steps to Reproduce:
1. Try to rebuild gfs2-utils (part of the cluster source rpm) on a Workstation, Client, or ComputeNode RHEL6 system.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2011-03-21 19:07:53 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.


Note You need to log in before you can comment on or make changes to this bug.