tarantool / tarantool/installer.sh
installer.sh: install tarantool using exact version
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
In GitLab by @Totktonada on Nov 9, 2020, 04:51
Sometimes a distro contains newer tarantool than a repository offers. However it is counter-intuitive when, say, you want to install 1.10, but 2.5 comes without any warnings.
I overcome the problem for tarantool-php CI this way: tarantool/tarantool-php@176d49f . Here I also verify the installed version against the requested one.
In GitLab by @Totktonada on Nov 9, 2020, 04:54
Filed the related issue for the manual instructions: tarantool/doc#1639
In GitLab by @Totktonada on Feb 11, 2021, 20:06
Now stable 2.6 is out and the problem is not so hot.
Aside of this, @artembo said that he increased priority of the installed repositories (both for Debian based and RHEL allied distributions) in installer.sh, so it should work correctly even for 1.10.
I guess the problem persists with manual installation instructions for 1.10.
This should become less painful with upcoming release policy renew: we will not offer 'unstable releases' as releases anymore. So distro maintainer will pick up a correct release (not newer than on our website). OTOH, it solves the problem only for a most recent series (2.6 for now, series 2 in the future), but not for, say, 1.10. Manual instructions still require an update.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting installer.sh, focusing on the Debian-based and RHEL-related installation paths mentioned in the issue. Compare the approach referenced in tarantool-php@176d49f and the manual-installation concern; done means requesting a Tarantool series does not silently install a newer incompatible version and the installed version is checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100