Description of problem: Alpha 12 is now available.
I know :-) http://play0ad.com/alpha-12-loucetios/#more-2684 Unless I find some really difficult problem, it should be updated before Sunday.
I plan to make two updates, because now nvidia-texture-tools was approved in Fedora, see #823096 The idea is one update for 0ad and 0ad-data, and another for nvidia-texture-tools. Once nvidia-texture-tools is in the stable repositories another 0ad update can be done.
You could also just build nvidia-texture-tools and add it to the buildroot with an override: https://admin.fedoraproject.org/updates/override/list After the next regeneration of the buildroot, you can then directly build the 0ad with proper support and do the update in one push.
(In reply to comment #3) > You could also just build nvidia-texture-tools and add it to the buildroot > with an override: > https://admin.fedoraproject.org/updates/override/list > > After the next regeneration of the buildroot, you can then directly build > the 0ad with proper support and do the update in one push. Note: select at least 2 days override. I apparently did request the override very close to midnight wherever the servers are, and override was active for like 10-15 min only :-)
moar info <pcpa_> How can I get again a buildroot override when I did select only one day override and was not aware it was close to midnight, and override was active for only 10-15 min? <pcpa_> Trying again it says a override already exists... <pcpa_> I did add override to f16, f17 and f18, but only managed to build for f16 and f18, f17 override was untagged before finishing building the chroot * dhaval has quit (Ping timeout: 248 seconds) <kalev> pcpa_: try to find the expired override in the Bodhi web ui and extend its duration * mejla (~mejla.upcbroadband.cz) has joined #fedora-devel <pcpa_> kalev: Many thanks! that did work :-)
0ad-0.0.12-2.fc16,0ad-data-0.0.12-1.fc16,nvidia-texture-tools-2.0.8-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/0ad-0.0.12-2.fc16,0ad-data-0.0.12-1.fc16,nvidia-texture-tools-2.0.8-3.fc16
0ad-0.0.12-2.fc17,0ad-data-0.0.12-1.fc17,nvidia-texture-tools-2.0.8-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/0ad-0.0.12-2.fc17,0ad-data-0.0.12-1.fc17,nvidia-texture-tools-2.0.8-3.fc17
0ad-0.0.12-2.fc18,0ad-data-0.0.12-1.fc18,nvidia-texture-tools-2.0.8-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/0ad-0.0.12-2.fc18,0ad-data-0.0.12-1.fc18,nvidia-texture-tools-2.0.8-3.fc18
Package 0ad-0.0.12-2.fc16, 0ad-data-0.0.12-1.fc16, nvidia-texture-tools-2.0.8-3.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 0ad-0.0.12-2.fc16 0ad-data-0.0.12-1.fc16 nvidia-texture-tools-2.0.8-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20773/0ad-0.0.12-2.fc16,0ad-data-0.0.12-1.fc16,nvidia-texture-tools-2.0.8-3.fc16 then log in and leave karma (feedback).
0ad-0.0.12-2.fc17, 0ad-data-0.0.12-1.fc17, nvidia-texture-tools-2.0.8-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
0ad-0.0.12-2.fc16, 0ad-data-0.0.12-1.fc16, nvidia-texture-tools-2.0.8-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
0ad-0.0.12-2.fc18, 0ad-data-0.0.12-1.fc18, nvidia-texture-tools-2.0.8-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.