Gemfile.lock在部署环境中具有不同版本的Rake

发布于 2025-01-04 21:10:03 字数 1119 浏览 1 评论 0原文

简而言之，错误消息如下所示：

$ bundle install
rake aborted!
You have already activated rake 0.9.2.2, but your Gemfile requires rake 0.9.2. Using bundle exec may solve this.

以下是此错误的解释：

部署服务器已安装 rake 0.9.2.2
应用程序 Gemfile 没有 Gemfile 所需的版本号 < code>rake
开发者的开发环境安装了 rake 0.9.2，此版本号位于 Gemfile.lock 文件中
部署服务器安装了许多 Rails 应用
程序应用程序是由不同的程序员
这些程序员在他们的开发环境中安装了不同的rake版本，
其中一些有rake 0.9.2，另一些有rake 0.9.2.2
通过阅读耶胡达·卡茨的澄清 .gemspec 和 Gemfile 的角色，Gemfile.lock 文件位于我们的 subversion

可能的解决方案：

错误消息可以通过运行 bundle 来避免exec rake install 然后，如果我们要求所有开发人员在 Gemfile 中指定相同版本的 rake，则可以避免 bundle update
消息
错误耙

我的问题是：这是正确的解决方案吗？或者有什么正确的解决方案吗？

我仍然不确定 Gemfile.lock 文件应该在 subversion 中。

原文

In short, the error message looks like following:

$ bundle install
rake aborted!
You have already activated rake 0.9.2.2, but your Gemfile requires rake 0.9.2. Using bundle exec may solve this.

And here is the explanation for this error:

deployment server has rake 0.9.2.2 installed
application Gemfile has no required version number for rake
developer's development environment has rake 0.9.2 installed and this version number is in Gemfile.lock file
deployment server has a number of rails applications installed
these applications are written by different programmers
these programmers have different rake version installed in their development environment
Some of them have rake 0.9.2 and others have rake 0.9.2.2
By reading Yehuda Katz's Clarifying the Roles of the .gemspec and Gemfile, Gemfile.lock file is in our subversion

Possible Solutions:

error message could be avoided by running bundle exec rake install then bundle update
error message could be avoided if we asked all developers to specify same version of rake in Gemfile
ask all developers to use same version of rake

My question is: is this the correct solution here? or is there any correct solutions?

I am still not really sure the Gemfile.lock file should be in subversion.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

半夏半凉 2025-01-11 21:10:03

您绝对应该检查您的 Gemfile.lock。它包含您知道可与您的应用程序配合使用的 gem 版本。因此，当您在不同的环境上捆绑安装时，您知道它应该可以工作。

假设几个月后有人在没有 Gemfile.lock 的情况下进行捆绑安装。他们将在您的 Gemfile 中获取最新版本的 gem（至少是具有指定版本的gems），并且无法保证您的应用程序甚至可以使用这些 gem。使用 Gemfile.lock，应该可以保证您的应用程序应该运行，因为任何使用过它或对其进行测试的人都应该将其与那些冻结的 gem 版本一起处于通过状态。

要解决您的问题，我会这样做：

bundle update rake

然后提交 Gemfile 和 Gemfile.lock。这样你就可以告诉任何运行你的应用程序的人你应该使用 0.9.2.2 的 rake。这是您知道将与您的应用程序配合使用的 rake 版本，并且您的测试将针对此版本运行。

要实际运行正确的版本，您有几个选项：

bundle exec：
```
$bundle exec rake -T
```

向 .bash_profile、.zshrc 或 .profile 添加别名也可能有帮助：

# in .bash_profile
alias b="bundle exec"
$ b rake -T

bundle binstubs

.bash_profile 中的

#
导出 PATH="./.bin:$PATH"
$ 捆绑安装--binstubs

这会将 Gemfile 的二进制文件安装到 ./bin 目录，并且路径更改将强制您的 shell 在查看 rvm 或 gem 安装二进制文件之前先签入 ./bin。如果执行此操作，请记住将“bin”添加到您的 .gitignore 文件中。

rubygems-bundler 宝石。这个 gem 生成包装器，尝试确定何时为您使用bundle exec。

You should definitely be checking in your Gemfile.lock. It contains the versions of your gem you know will work with your application. So when you bundle install on a different environment you know it should work.

Say a few months from now someone does a bundle install without a Gemfile.lock. They will get the latest version of gems in your Gemfile (at least the ones with a specified version) and there will be no guarantee that your app will even work with those gems. With a Gemfile.lock, there should be some assurance that your app should run, since anyone who's worked with it or ran tests on it should have had it in a passing state with those frozen gem versions.

To resolve your issue, I would do:

bundle update rake

and then commit Gemfile and Gemfile.lock. This way you're telling anyone who runs your app that you should be using 0.9.2.2 of rake. This is the version of rake you know will work with your app and your tests are run against this version.

To actually run the correct version you have a few options:

bundle exec:
```
$ bundle exec rake -T
```

Adding an alias to your .bash_profile, .zshrc, or .profile might also help:

# in .bash_profile
alias b="bundle exec"
$ b rake -T

bundle binstubs

# in your .bash_profile
export PATH="./.bin:$PATH"
$ bundle install --binstubs

This will install your Gemfile's binaries to ./bin directory and the path change will force your shell to check in ./bin first before looking in rvm or your gem install binaries. Remember to add 'bin' to your .gitignore file if you do this.