Latest upstream release: 0.10.0 Current version in Fedora Rawhide: 0.9.5 URL: http://sourceforge.net/api/file/index/project-name/freecol/mtime/desc/limit/20/rss Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.10.1 Current version in Fedora Rawhide: 0.9.5 URL: http://sourceforge.net/api/file/index/project-name/freecol/mtime/desc/limit/20/rss Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.10.3 Current version in Fedora Rawhide: 0.9.5 URL: http://sourceforge.net/api/file/index/project-name/freecol/mtime/desc/limit/20/rss Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
freecol-0.10.3-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/freecol-0.10.3-1.fc16
Package freecol-0.10.3-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing freecol-0.10.3-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14457 then log in and leave karma (feedback).
We've decided to not go with 0.10.x for F-16 due to various issue with it, see: https://admin.fedoraproject.org/updates/FEDORA-2011-14457 Rawhide and F-17 will have 0.10.x, which then will hopefully have a bugfix release fixing the worst issues, closing this bug.
*** Bug 781330 has been marked as a duplicate of this bug. ***