On 10/11/2011 06:22 PM, Scott Seago wrote:
On 10/11/2011 03:52 PM, Mo Morsi wrote:
> On 10/11/2011 09:27 AM, Mo Morsi wrote:
>>> mfojtik: deltacloud
>>>
>>> sloranz: imagefactory, aeolus-image (if you are not able to get push
>>> rights in the next day or two, I will take these over myself)
>> Quick adjustment here, since Steve informed he does not maintain the
>> aeolus-image code, it'd be best to reassign this to someone that does,
>> jayg would you be fine with taking care of this from here on out?
>>
>>
> OK mtaylor agreed to take care of this. Unfortunately he isn't sponsored
> yet, so I went ahead and pushed aeolus-image and imagefactory into F16
> via bodhi
>
>
https://admin.fedoraproject.org/updates/rubygem-aeolus-image-0.1.0-3.fc16
>
>
https://admin.fedoraproject.org/updates/imagefactory-0.7.0-1.fc16
>
> These and aeolus-configure have a relatively low karma (1). So if
> someone wants to give them a bump, they will be pushed to stable
> immediately.
>
> -Mo
And to round out the list, conductor has been pushed as well (same karma
comments as above):
https://admin.fedoraproject.org/updates/aeolus-conductor-0.4.0-1.fc16
Scott
So as it turns out I hit a couple of dep problems here:
1) I forgot about aeolus-all, which must be updated concurrently. I'll
add this one to the mix tomorrow once I'm approved for aeolus-all
commits by clalance or mmorsi
2) Apparently rubygem-oauth isn't in fedora. I don't see it listed as a
valid package, although I do see that there's a package review ticket
for it that succeeded.
Mo -- is there any chance we can get oauth pushed in this week --
without it we can't test conductor 0.4.0 in Fedora.
Scott