Bug 514350

Summary: RFE: gobby 0.5.0 (status request)
Product: [Fedora] Fedora Reporter: Ben Boeckel <fedora>
Component: gobbyAssignee: Luke Macken <lmacken>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: lmacken, opensource, pfrields, samuel-rhbugs, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-22 19:01:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Boeckel 2009-07-28 22:45:42 UTC
I have packaged libinfinity (#507070) and I would like this bug to track the status of gobby's update to 0.5.x. I can offer testing for when it hits rawhide/updates-testing alongside Kobby as well.

Comment 1 Till Maas 2010-03-30 11:11:18 UTC
I am also interested in running gobby 0.5 in Fedora. How about introducing gobby5 and libinfinity04 packages, that allow to install all in parallel? Afaics Kobby still needs libinfinity 0.3.x.

Comment 2 Ben Boeckel 2010-03-30 12:23:53 UTC
I haven't updated Kobby in a while. I can try to run things with libinfinity 0.4 and if it works, I'll update things so that Gobby and Kobby can use the same code.

Comment 3 Ankur Sinha (FranciscoD) 2012-03-06 13:43:58 UTC
Hello,

The last comment to this bug was back in 2010. Could anyone please post the current status?

According to the site: http://gobby.0x539.de/trac/
2011-03-28: libinfinity 0.5.0 and Gobby 0.4.94 released 

I assume that means they're stable :)
Could we update to this?

Thanks,
Ankur

Comment 4 Till Maas 2012-07-22 19:01:03 UTC
Gobby 0.5 can be installed in parallel, therefore I created a review request for it:
https://bugzilla.redhat.com/show_bug.cgi?id=842172

*** This bug has been marked as a duplicate of bug 842172 ***