# How to fix bundler executable conflicts in the \`techAPJ/install-rails\` script?

**URL:** <https://meta.discourse.org/t/how-to-fix-bundler-executable-conflicts-in-the-techapj-install-rails-script/76717>\
**Category:** Development\
**Created:** [December 24, 2017, 11:37pm UTC](https://meta.discourse.org/t/how-to-fix-bundler-executable-conflicts-in-the-techapj-install-rails-script/76717 "2017-12-24T23:37:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [December 25, 2017, 12:05am UTC](https://meta.discourse.org/t/how-to-fix-bundler-executable-conflicts-in-the-techapj-install-rails-script/76717/2 "2017-12-25T00:05:43Z")

</div>

It has been a couple years since I got a “update bundler” prompt. I figured “latest is best” and upgraded bundler.

Unfortunely, at that time, some of what Discourse needed to be in bundler was not in the upgraded bundler. I had to start over and _ignore_ that with a _no_

But “linux” last got a commit a month ago, so I would guess it should be OK to upgrade bundler. Worse case, you will need to start over. Else wait for techAPJ to reply.

[https://github.com/techAPJ/install-rails](https://github.com/techAPJ/install-rails)

---

_[View the full topic](https://meta.discourse.org/t/how-to-fix-bundler-executable-conflicts-in-the-techapj-install-rails-script/76717)._