Closed zackse closed 5 years ago
the tags in the git-repo should NOT contian the LuaRocks rockspec revision number. So this change is valid.
But to get this done, the rockspec should be renamed with an incremented LR revision number; -1
in this case. And then that rockspec should be pushed/published to the LuaRocks server.
(the quick and dirty fix would be to create another tag 2.0.0-0
(on the same commit as currently tagged 2.0.0
)
replaced by #603
this can be closed now since #603 was merged
Thanks for the quick fix in #603.
As of the new release, the version referenced in the rockspec file's source URL is inaccessible. This commit changes it to match the tarball version on github (no
-0
suffix). I'm not sure if this is preferable to renaming the archive and its contained directory, but it works in local testing.