You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: