Tim Caswell
Tim Caswell
See also https://github.com/torch/torch7/issues/1035 Seems to be a problem with luajit itself.
For now the way to delete a package is to tell me directly and I'll remove it manually. We could add this feature, but it would need to be carefully...
ok, deleted. I ran `rm -r bakpakin/moonmint-router/ bakpakin/moonmint-request/ bakpakin/moonmint-response/` in the `refs/tags` folder.
make sure to delete them in your local `.litdb` folder or they might publish again if you make updates and publish them.
Hmm, I saw this too and couldn't find the cause quickly. There is a workaround by building luvit directly. ``` sh # assuming bash-like shell lit make lit://luvit/luvit `which luvit`...
But I suspect the root problem will persist, so we should probably find the cause. I'll try to look at it tomorrow.
Yes, the solution will be to detect a homebrew install and disable update in that case. We'll print a nice message to the user that they need to update via...
Let me know if this patch helps.
You might have a package in your local cache that was signed improperly or not signed at all. Try nuking the local cache and trying again. Make sure you've done...
`lit auth` takes a more direct path, but both should use the auto-config logic that was broken for anyone using custom private key paths. I just published lit 2.2.17 with...