blocks|key|2099204|text|只要运行gem+install+bundler:2.1.4，不要担心与ruby一起的旧版本，它不应该被使用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2099205|entityMap^0|4|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Just run <code>gem install bundler:2.1.4</code>, don't worry about the older version that comes with ruby, it should not be used.

blocks|key|2099229|text|，gem更新--系统帮我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2099230|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

per Anne van Rossum,
gem update --system
fixed this problem for me.

blocks|key|1086794|text|我修好了！如果您正在使用rvm，那么您必须转向在特定项目中使用的ruby版本(例如。‘'rvm使用2.7.0')，然后运行’宝石更新-系统‘|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1086795|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I fixed it!. If you are using rvm, then you have to turn to the ruby version you are using on that particular project (eg. 'rvm use 2.7.0') and then run 'gem update --system'

blocks|key|1086859|text|您需要执行以下操作，以确保正确的默认版本的Bundler用于正在使用的回购。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1086860|1086861|You可以运行以下内容，但这可能会出现问题，因为它会破坏系统上的本地资源，因为它们都会被更新。|ordered-list-item|offset|length|style|BOLD|1086862|1086863|gem更新--system|1086864|1086865|下面的方法是确保邦德勒更新|1086866|的一种更安全的方法|1086867|INSTALLATION_DIRECTORY+|1086868|获取gem环境并注意到gem环境|unordered-list-item|1086869|1086870|然后运行以下cd+//|1086871|-<_default_version>.+gem安装-默认绑定程序-v+-v|1086872|1086873|如果您遵循了2，但仍然不能工作，那么运行|1086874|+bundler:|1086875|1086876|以确保您的本地回购使用正确的版本|1086877|entityMap^0|0|0|0|1B|0|0|0|D|0|0|0|D|0|0|9|0|0|M|0|0|G|0|0|0|B|1|0|12|1|0|0|K|0|0|9|0|0|0|G|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1D|8|@$F|1E|G|1F|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1H|8|@$F|1I|G|1J|H|I]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1L|8|@$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1O|8|@$F|1P|G|1Q|H|I]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1R|8|@$F|1S|G|1T|H|I]]|9|@]|A|$]]|$1|T|3|U|5|V|7|1U|8|@$F|1V|G|1W|H|I]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1Y|8|@$F|1Z|G|20|H|I]]|9|@]|A|$]]|$1|Z|3|10|5|V|7|21|8|@$F|22|G|23|H|I]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|25|8|@$F|26|G|27|H|I]]|9|@]|A|$]]|$1|14|3|15|5|E|7|28|8|@$F|29|G|2A|H|I]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2C|8|@$F|2D|G|2E|H|I]]|9|@]|A|$]]|$1|19|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]]|1A|$]]

You need to do the following to ensure the correct default version of Bundler is used for the repo you are working with.
<ol>
<li>You can run the following but this can present issues as it can break your local gems on your system as ALL of them are updated.
<pre><code>gem update --system
</code></pre>
</li>
<li>The following method is a much safer way of ensuring Bundler is updated
</li>
</ol>
<ul>
<li>Get your gem environment and take note of INSTALLATION_DIRECTORY
<pre><code>gem environment
</code></pre>
</li>
<li>Then run the following
<pre><code>cd &lt;INSTALLATION DIRECTORY&gt;/specifications/default
rm bundler-&lt;old_default_version&gt;.gemspec
gem install --default bundler -v &lt;new_default_version&gt;
</code></pre>
</li>
</ul>
<ol start="3">
<li>If you have followed 2 and that still does not work, then run
<pre><code>gem install bundler:&lt;new_default_version&gt;
</code></pre>
to ensure you your local repo is using the correct version</li>
</ol>

blocks|key|2099356|text|另一种选择是更新到最新版本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2099357|gem+update+bundler|code-block|syntax|javascript|2099358|除非有使用旧版本的特定原因(例如，最新版本中有错误，或者它们不再兼容)，否则您可以按照警告消息安装该特定版本：|2099359|2099360|警告:正在运行的邦德勒版本(2.2.32)比创建锁文件的版本(2.3.4)要早。我们建议您通过运行gem+install+bundler:2.3.4升级到创建锁文件的版本。|blockquote|offset|length|style|CODE|2099361|2099362|2099363|gem+install+bundler:2.3.4|2099364|entityMap^0|0|0|0|0|1D|P|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|10|8|@$M|11|N|12|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|V|$]]

Another option is to update to the latest version:
<pre><code>gem update bundler
</code></pre>
Unless there is a specific reason for using an older version (for example, there is a bug in the latest version, or they are no longer compatible), then you can follow the warning message to just install that particular version:
<blockquote>
Warning: the running version of Bundler (2.2.32) is older than the version that created the lockfile (2.3.4). We suggest you to upgrade to the version that created the lockfile by running <code>gem install bundler:2.3.4</code>.
</blockquote>
<pre><code>gem install bundler:2.3.4
</code></pre>

blocks|key|1086975|text|在我的例子中，这是在失败的安装上显示的唯一错误消息。我浪费了很多时间来修复它，但是事实证明，只是一个警告，而不是阻止安装的实际错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1086976|要查看实际的错误消息，我必须运行bundle+install+--verbose|CODE|1086977|entityMap^0|1A|K|0|G|O|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|N|8|@$9|O|A|P|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|J|$]]

In my case, this was the only error-message being shown on a failed install. I wasted a lot of time trying to fix it, but it turns out it's just a warning, not an actual error that blocks the install.
To see the actual error message, I had to run <code>bundle install --verbose</code>

blocks|key|2099449|text|Ruby提供了一组默认的宝石。邦德勒就是其中之一。随Ruby一起发布的default+version+of+很快就会过时。若要更新标准宝石，请运行|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2099450|gem+update+--system|code-block|syntax|javascript|2099451|有关更多信息，请参见+command+reference。|2099452|如果您不想更新您的标准宝石，也可以在包(Gemfile.lock)的上下文中更新Bundler。这是可能的since++v1.14。|style|CODE|2099453|bundle+update+--bundler|2099454|2099455|这一警告的时间应该超过since++v2.3.5+(2022年1月)。它现在自动获取匹配的远程版本并安装它。|2099456|Bundler+2.3.17+is+running,+but+your+lockfile+was+generated+with+2.3.7.+Installing+Bundler+2.3.7+and+restarting+using+that+version.
Fetching+gem+metadata+from+https://rubygems.org/.
Fetching+bundler+2.3.7
Installing+bundler+2.3.7
…|2099457|entityMap|0|LINK|mutability|MUTABLE|url|https://stdgems.org/bundler/#gem-version|1|https://guides.rubygems.org/command-reference/|2|https://bundler.io/v1.14/man/bundle-update.1.html#OPTIONS|3|https://github.com/rubygems/rubygems/commit/ab1e3e5236f469c5f45d3f821a578335c41c89d6^0|Z|J|0|0|0|A|I|1|0|K|C|1H|C|2|0|0|0|B|D|3|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|D|3|E|5|F|7|1D|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|K|3|L|5|6|7|1I|8|@$A|1J|B|1K|M|N]]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|O|3|P|5|F|7|1O|8|@]|9|@]|C|$G|H]]|$1|Q|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1Q|8|@]|9|@$A|1R|B|1S|1|1T]]|C|$]]|$1|T|3|U|5|F|7|1U|8|@]|9|@]|C|$G|H]]|$1|V|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]|15|$5|Y|Z|10|C|$11|16]]|17|$5|Y|Z|10|C|$11|18]]]]

Ruby ships with a default set of gems. Bundler is one of them. The <a href="https://stdgems.org/bundler/#gem-version" rel="nofollow noreferrer">default version of bundler</a> shipped with your Ruby tends to be outdated soon. To update your standard gems, run
<pre class="lang-bash prettyprint-override"><code>gem update --system
</code></pre>
See the <a href="https://guides.rubygems.org/command-reference/" rel="nofollow noreferrer">RubyGems command reference</a> for more information.
If you don't want to update your standard gems, you can also update Bundler in the context of your bundle (<code>Gemfile.lock</code>). This is possible <a href="https://bundler.io/v1.14/man/bundle-update.1.html#OPTIONS" rel="nofollow noreferrer">since Bundler v1.14</a>.
<pre class="lang-bash prettyprint-override"><code>bundle update --bundler
</code></pre>
<hr />
The times of this warning should be over <a href="https://github.com/rubygems/rubygems/commit/ab1e3e5236f469c5f45d3f821a578335c41c89d6" rel="nofollow noreferrer">since Bundler v2.3.5</a> (January 2022). It now automatically fetches the matching remote version and installs it.
<pre><code>Bundler 2.3.17 is running, but your lockfile was generated with 2.3.7. Installing Bundler 2.3.7 and restarting using that version.
Fetching gem metadata from https://rubygems.org/.
Fetching bundler 2.3.7
Installing bundler 2.3.7
…
</code></pre>

blocks|key|2099337|text|我删除了gemfile.lock文件，然后再次绑定以构建新的依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2099338|https://github.com/rubygems/rubygems/issues/3202|offset|length|2099339|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I removed gemfile.lock file then bundle again to build new dependencies.
<a href="https://github.com/rubygems/rubygems/issues/3202" rel="nofollow noreferrer">https://github.com/rubygems/rubygems/issues/3202</a>

When I'm developing/testing, I'm keep getting this error in my console

<pre><code>Warning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.1.4). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.1.4`.
</code></pre>

It's not blocking me at all but bugging me. I know that easiest solution is just updating my Gemfile.lock to this. 

<pre><code>BUNDLED WITH
 2.1.2
</code></pre>

But I want to solve this permanently. I try to

<pre><code>gem uninstall bundler
</code></pre>

and then

<pre><code>gem install bundler -v 2.1.4
</code></pre>

It keeps me giving this error

<pre><code>Gem bundler-2.1.2 cannot be uninstalled because it is a default gem
</code></pre>

and when I try to first install 2.1.4 and then delete bundler 2.1.2 console gives me this output.

<pre><code>Gem bundler-2.1.2 cannot be uninstalled because it is a default gem
Successfully uninstalled bundler-2.1.4
</code></pre>

Is there any solution to this problem? Thanks in advance

Warning: the running version of Bundler is older than the version that created the lockfile error

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

当我开发/测试时，我总是在我的控制台中得到这个错误Warning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.1.4). We suggest you to upgrade to the version that created the lockfile

问警告:正在运行的邦德勒版本比创建锁文件错误的版本要早。
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问警告:正在运行的邦德勒版本比创建锁文件错误的版本要早。EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问警告:正在运行的邦德勒版本比创建锁文件错误的版本要早。
EN