Bug 847220 - Please update rubygem-rbovirt in F17 to >=0.0.12
Please update rubygem-rbovirt in F17 to >=0.0.12
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: rubygem-rbovirt (Show other bugs)
17
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Vít Ondruch
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-10 03:28 EDT by Michal Fojtik
Modified: 2012-08-21 05:56 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-08-21 05:56:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Fojtik 2012-08-10 03:28:20 EDT
Description of problem:

The version of rbovirt is outdated and Deltacloud require features that are available from >0.0.10. Is it possible to update this gem.

Expected results:

Version 0.0.12 will land in Fedora updates.
Comment 1 Fedora Update System 2012-08-10 03:42:13 EDT
rubygem-rbovirt-0.0.12-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/rubygem-rbovirt-0.0.12-1.fc17
Comment 2 Fedora Update System 2012-08-10 18:34:08 EDT
Package rubygem-rbovirt-0.0.12-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rubygem-rbovirt-0.0.12-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11731/rubygem-rbovirt-0.0.12-1.fc17
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-08-21 05:56:59 EDT
rubygem-rbovirt-0.0.12-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

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