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
Rails 7.0.8.4 incompatible with crypt_keeper 2.3.0 (rubygems.org)
Because rails < 7.1.0 depends on activerecord = 7.0.8.4 and rails >= 7.1.0, < 7.1.1 depends on activesupport = 7.1.0, rails < 7.1.1 requires activerecord = 7.0.8.4 or activesupport = 7.1.0. And because rails >= 7.1.1, < 7.1.2 depends on activesupport = 7.1.1 and rails >= 7.1.2, < 7.1.3 depends on activesupport = 7.1.2, rails < 7.1.3 requires activerecord = 7.0.8.4 or activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2. And because rails >= 7.1.3, < 7.1.3.1 depends on activesupport = 7.1.3 and rails >= 7.1.3.1, < 7.1.3.2 depends on activesupport = 7.1.3.1, rails < 7.1.3.2 requires activerecord = 7.0.8.4 or activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1. And because rails >= 7.1.3.2, < 7.1.3.3 depends on activesupport = 7.1.3.2 and rails >= 7.1.3.3, < 7.1.3.4 depends on activesupport = 7.1.3.3, rails < 7.1.3.4 requires activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1 OR = 7.1.3.2 OR = 7.1.3.3 or activerecord = 7.0.8.4. And because rails >= 7.1.3.4 depends on activesupport = 7.1.3.4 and crypt_keeper >= 2.3.0 depends on activerecord >= 4.2, <= 7, crypt_keeper >= 2.3.0 requires activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1 OR = 7.1.3.2 OR = 7.1.3.3 OR = 7.1.3.4. So, because crypt_keeper >= 2.3.0 depends on activesupport >= 4.2, <= 7 and Gemfile depends on crypt_keeper ~> 2.3, version solving has failed.
Pulling the gem from the current master fixes this problem (from the specific ref commit), but there are no compatible gems in rubygems.org that address this Rails 7.0.x issue:
Rails 7.0.8.4 incompatible with crypt_keeper 2.3.0 (rubygems.org)
Because rails < 7.1.0 depends on activerecord = 7.0.8.4 and rails >= 7.1.0, < 7.1.1 depends on activesupport = 7.1.0, rails < 7.1.1 requires activerecord = 7.0.8.4 or activesupport = 7.1.0. And because rails >= 7.1.1, < 7.1.2 depends on activesupport = 7.1.1 and rails >= 7.1.2, < 7.1.3 depends on activesupport = 7.1.2, rails < 7.1.3 requires activerecord = 7.0.8.4 or activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2. And because rails >= 7.1.3, < 7.1.3.1 depends on activesupport = 7.1.3 and rails >= 7.1.3.1, < 7.1.3.2 depends on activesupport = 7.1.3.1, rails < 7.1.3.2 requires activerecord = 7.0.8.4 or activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1. And because rails >= 7.1.3.2, < 7.1.3.3 depends on activesupport = 7.1.3.2 and rails >= 7.1.3.3, < 7.1.3.4 depends on activesupport = 7.1.3.3, rails < 7.1.3.4 requires activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1 OR = 7.1.3.2 OR = 7.1.3.3 or activerecord = 7.0.8.4. And because rails >= 7.1.3.4 depends on activesupport = 7.1.3.4 and crypt_keeper >= 2.3.0 depends on activerecord >= 4.2, <= 7, crypt_keeper >= 2.3.0 requires activesupport = 7.1.0 OR = 7.1.1 OR = 7.1.2 OR = 7.1.3 OR = 7.1.3.1 OR = 7.1.3.2 OR = 7.1.3.3 OR = 7.1.3.4. So, because crypt_keeper >= 2.3.0 depends on activesupport >= 4.2, <= 7 and Gemfile depends on crypt_keeper ~> 2.3, version solving has failed.
Pulling the gem from the current master fixes this problem (from the specific ref commit), but there are no compatible gems in rubygems.org that address this Rails 7.0.x issue:
gem 'crypt_keeper', git: 'https://github.com/jmazzi/crypt_keeper.git', ref: '1a1d7fe'
If you could upload a new crypt_keeper version to ruby gems from this commit 1a1d7fe, it would fix the issue for this Rails 7.0.x
The text was updated successfully, but these errors were encountered: