uqm-0.6.2-8.fc11.x86_64 uqm's autodownloader seems to be failing to download its content. I don't see any traffic. After a long while it fails with a pop-up window: MD5Sum has failed! Press 'Redownload' to redownload the files. Press 'Quit' to quit.
Perhaps uqm is better moving wholesale into rpmfusion? Then you can have the entire game + content in RPMS again, and not rely upon unreliable third parties like this.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The bug is caused by wrong download urls in file: /usr/uqm.autodlrc It uses non-functional download.sourceforge.net, where it should use prdownloads.sourceforge.net .
I have found that even when the content file is manually downloaded and installed, the /usr/bin/uqm script still launches the content downloader. After install the content manually, I changed /usr/bin/uqm to read: #!/bin/sh # Wrapper script for starting The Ur-Quan Masters exec /usr/games/uqm -n /usr/share/uqm/content It would be nice to see either the script fixed or the whole UQM pacakge set moved to RPMFusion.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
uqm-0.6.2-11.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/uqm-0.6.2-11.fc12
uqm-0.6.2-11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/uqm-0.6.2-11.fc11
uqm-0.6.2-11.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/uqm-0.6.2-11.fc13
uqm-0.6.2-11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update uqm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/uqm-0.6.2-11.fc11
uqm-0.6.2-11.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update uqm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/uqm-0.6.2-11.fc12
uqm-0.6.2-11.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
uqm-0.6.2-11.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
uqm-0.6.2-11.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.