Bug 807727 - aeolus-conductor should not depend on rubygem(sqlite3)
Summary: aeolus-conductor should not depend on rubygem(sqlite3)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta6
Assignee: Steve Linabery
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 15:06 UTC by Hugh Brock
Modified: 2012-05-15 22:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:59:05 UTC

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:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Hugh Brock 2012-03-28 15:06:30 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 wes hayutin 2012-03-28 15:11:00 UTC 
aeolus-conductor should not depend on rubygem(sqlite3)

rpm issue.. no description needed :)
Comment 2 Steve Linabery 2012-03-28 15:36:31 UTC 
5ad906d814e46bf09eb445bc6fd153a113b7f403 master
9b1de4b48a378151010be709da1b2fd7098601f8 0.9-maint/1.0-product
Comment 4 Rehana 2012-04-04 14:10:11 UTC 
Observed that rubygem-sqlite3 has been removed from the repo

[root@ibm-ls41-02 ~]# repoquery -q rubygem-sqlite3 --whatrequires
[root@ibm-ls41-02 ~]# 

hence moving the status to verified.

info:

rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-0.8.7-1.el6.noarch
aeolus-conductor-doc-0.8.7-1.el6.noarch
aeolus-conductor-daemons-0.8.7-1.el6.noarch
aeolus-configure-2.5.2-1.el6.noarch
aeolus-all-0.8.7-1.el6.noarch
rubygem-aeolus-cli-0.3.1-1.el6.noarch
Comment 6 errata-xmlrpc 2012-05-15 22:59:05 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-0583.html
Note You need to log in before you can comment on or make changes to this bug.