Bug 1200831 - Review Request: rubygem-fog-riakcs - Module for the 'fog' gem to support Riakcs
Summary: Review Request: rubygem-fog-riakcs - Module for the 'fog' gem to support Riakcs
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Josef Stribny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1152158
TreeView+ depends on / blocked
 
Reported: 2015-03-11 13:06 UTC by Vít Ondruch
Modified: 2016-01-04 05:54 UTC (History)
3 users (show)

Fixed In Version: rubygem-fog-riakcs-0.1.0-1.fc23
Clone Of:
Environment:
Last Closed: 2015-03-19 13:05:41 UTC
Type: ---
Embargoed:
jstribny: fedora-review+
gwync: fedora-cvs+

Attachments (Terms of Use)

Description Vít Ondruch 2015-03-11 13:06:55 UTC 
Spec URL: https://fedorapeople.org/cgit/vondruch/public_git/rubygem-fog-riakcs.git/tree/rubygem-fog-riakcs.spec?id=35fdf1b191c4e26619c40ebc7053fc83066930cf
SRPM URL: http://people.redhat.com/vondruch/rubygem-fog-riakcs-0.1.0-1.fc23.src.rpm
Description: This library can be used as a module for `fog` or as standalone provider to use the Riakcs in applications.
Fedora Account System Username: vondruch

Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=9204002
Comment 1 Josef Stribny 2015-03-13 07:54:56 UTC 
Taking.
Comment 2 Josef Stribny 2015-03-13 08:06:53 UTC 
The spec looks good, package builds, installs, runs. Tests are passing =>  APPROVED.
Comment 3 Vít Ondruch 2015-03-13 13:16:33 UTC 
New Package SCM Request
=======================
Package Name: rubygem-fog-riakcs
Short Description: Module for the 'fog' gem to support Riakcs
Upstream URL: 
Owners: vondruch
Branches: https://github.com/fog/fog-riakcs
InitialCC:
Comment 4 Gwyn Ciesla 2015-03-13 13:47:52 UTC 
Git done (by process-git-requests).

Moved URL from branches to URL. :)
Comment 5 Vít Ondruch 2015-03-19 12:54:09 UTC 
(In reply to Jon Ciesla from comment #4)
> Moved URL from branches to URL. :)

Hups ... cannot imagine how that could happened. Thanks for fixing this for me :)
Note You need to log in before you can comment on or make changes to this bug.