Latest upstream release: 2.0.12 Current version in Fedora Rawhide: 2.0.11 URL: http://luarocks.org/releases/ 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
luarocks-2.0.12-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/luarocks-2.0.12-1.fc16
luarocks-2.0.12-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/luarocks-2.0.12-1.fc18
luarocks-2.0.12-1.el6.1 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/luarocks-2.0.12-1.el6.1
luarocks-2.0.12-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/luarocks-2.0.12-1.fc17
luarocks-2.0.12-1.el5.1 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/luarocks-2.0.12-1.el5.1
Package luarocks-2.0.12-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing luarocks-2.0.12-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17610/luarocks-2.0.12-1.fc18 then log in and leave karma (feedback).
luarocks-2.0.12-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
luarocks-2.0.12-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
luarocks-2.0.12-1.el5.1 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
luarocks-2.0.12-1.el6.1 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.