It has released new version for a long time (0.6.8 now) Please update, or release your ownership.
Hi Christopher, I have stopped actively maintaining the packages. Would you like to take over the ownership? Thanks
Contact in private.
@chris I just tried to build the new version, but I don't want to take ownership yet, as I am not familiar with this package. Please find my spec file at https://github.com/bbbush/Fedora/tree/wxGlade with commit Id b6c2d7ba709cb4, thanks
(In reply to Yijun Yuan from comment #3) > @chris I just tried to build the new version, but I don't want to take > ownership yet, as I am not familiar with this package. Please find my spec > file at > > https://github.com/bbbush/Fedora/tree/wxGlade with commit Id b6c2d7ba709cb4, > thanks Hi Yuan nice to meet you again. I'm talking with Mr.Miao in private, will feedback later.
@Christopher, I have granted all your commit acl requests, and also released my ownership of this package. Thanks for taking the initiative of moving things forward.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
wxGlade-0.6.8-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/wxGlade-0.6.8-1.fc19
wxGlade-0.6.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/wxGlade-0.6.8-1.fc20
Package wxGlade-0.6.8-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wxGlade-0.6.8-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16391/wxGlade-0.6.8-1.fc20 then log in and leave karma (feedback).
wxGlade-0.6.8-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
wxGlade-0.6.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.