rockspec: sync rockspecs with rocks.tarantool.org #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make lulpeg rockspecs, which are stored there, consistent with
rocks.tarantool.org ones. I don't know, whether there is a reason to
store rockspecs in the repository, but I see that we do. So let them be
in-sync with ones on the server.
See the relevant changes in tarantool/rocks:
After this, the rocks server goes to
https://github.com/tarantool/rocks.tarantool.org and rockspec changes on
the server are not tracked in git anymore (usually updated in
repositories and published to the server from CI).
After the transition we changed
git://
URLs togit+https://
, seehttps://github.blog/2021-09-01-improving-git-protocol-security-github/
for reasons.
Part of tarantool/tarantool#6587