My company has a setup where a librarian installation is managed by bundler and cannot be loaded as bundler and thor have a dependency conflict.
We use Bundler in version 2.1.4 in a Ruby 2.4 environment. Yes, i know, Ruby 2.4 is outdated and unsupported.
Anyhow, while Bundle in 2.x requires any thor version >=0 (which is the latest major) and is installed first as gem management tool librarian defined its thor dependency as ~>0.15. This means: Take the latest minor which >= 0.15. This happens to be thor 0.20.x .
I cannot resolve the conflict as my test scenario with kitchen-docker and kitchen-ansible requires both bundler and librarian (for librarian-ansible).
Understanding dependencies in ruby is hard for me but this is what i understood from my environment. Uninstalling thor 1.x did successfully link/activate the librarian gem.
My company has a setup where a librarian installation is managed by bundler and cannot be loaded as bundler and thor have a dependency conflict.
We use Bundler in version 2.1.4 in a Ruby 2.4 environment. Yes, i know, Ruby 2.4 is outdated and unsupported.
Anyhow, while Bundle in 2.x requires any thor version >=0 (which is the latest major) and is installed first as gem management tool librarian defined its thor dependency as ~>0.15. This means: Take the latest minor which >= 0.15. This happens to be thor 0.20.x .
I cannot resolve the conflict as my test scenario with kitchen-docker and kitchen-ansible requires both bundler and librarian (for librarian-ansible).
Understanding dependencies in ruby is hard for me but this is what i understood from my environment. Uninstalling thor 1.x did successfully link/activate the librarian gem.