I am trying to install fat free crm on a Windows 10 machine, but so far I have been unsuccessful. This is my latest attempt. Any help will be greatly appreciated.
Running bundler install gives me these messages:
Bundler 2.3.7 is running, but your lockfile was generated with 2.3.10. Installing Bundler 2.3.10 and restarting using that version.
Fetching gem metadata from https://rubygems.org/.
Fetching bundler 2.3.10
Installing bundler 2.3.10
Fetching gem metadata from https://rubygems.org/.........
Lots of successfully installed gems later:
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory:
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/libv8-node-16.10.0.0/ext/libv8-node
C:/Ruby31-x64/bin/ruby.exe -I C:/Ruby31-x64/lib/ruby/3.1.0 -r
./siteconf20221119-16700-fgt0qd.rb extconf.rb
creating Makefile
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/libv8-node-16.10.0.0/ext/libv8-node/builder.rb:12:in
`build_libv8!': failed to download node 16.10.0 (Libv8::Node::BuilderError)
from
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/libv8-node-16.10.0.0/ext/libv8-node/location.rb:30:in
`install!'
from extconf.rb:9:in `<main>'
==== in
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/libv8-node-16.10.0.0/ext/libv8-node
==== running
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/libv8-node-16.10.0.0/libexec/download-node
extconf failed, exit code 1
My node version is v18.12.1, by the way. (Do I need an older one?)
Anyway, here is the exact sequence of actions before running bundler install inside my local git clone of fat_free_crm:
First, the repository I am using:
https://github.com/fatfreecrm/fat_free_crm
My Ruby version:
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt]
For a fresh start, I uninstall all gems, including rails:
gem uninstall -aIx
The latest commit on the bin folder says: Upgrade to Rails 6 so I install the latest rails 6 version on my machine:
gem install rails -v 6.1.7
I clone the repository from github:
git clone https://github.com/fatfreecrm/fat_free_crm.git
Since I am using sqlite3 for this, I comment out all other db gems in the Gemfile and only leave this one:
gem 'sqlite3', '~> 1.4.0'
Then, I copy database.sqlite.yml into database.yml.
Then, I run bundler install from within the directory fat_free_crm, which gives me this:
Ensure you have either installed the shared-mime-info package for your distribution, or
obtain a version of freedesktop.org.xml and set FREEDESKTOP_MIME_TYPES_PATH to the location of that file.
I (hopefully) solved that problem with this stackoverflow solution: Error installing ruby on rails on windows 10
Afterwards, I run bundler install again, which gives the error messages that I mentioned at the top of my description.
Any help will be greatly appreciated.
P.S.: I am trying to get back into Ruby on Rails after a long break, so please forgive me, if I made any stupid mistakes.
I'm working with heroku and every time I try to push my app this message shows out:
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote:
remote: !
remote: ! You must use Bundler 2 or greater with this lockfile.
remote: !
remote: /tmp/d20181109-104-g861yi/bundler-1.15.2/gems/bundler-1.15.2/lib/bundler/lockfile_parser.rb:108:in `warn_for_outdated_bundler_version': You must use Bundler 2 or greater with this lockfile. (Bundler::LockfileError)
remote: from /tmp/d20181109-104-g861yi/bundler-1.15.2/gems/bundler-1.15.2/lib/bundler/lockfile_parser.rb:95:in `initialize'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:130:in `new'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:130:in `block in parse_gemfile_lock'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/vendor/ruby/heroku-18/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:16:in `instrument'
remote: from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/helpers/bundler_wrapper.rb:86:in `instrument'
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to my-proyect-1234.
remote:
It says 'remote: ! You must use Bundler 2 or greater with this lockfile.'
But my Bundler version is 2.0.0.pre.1
Don't know what to do, I tried uninstalling bundle and installing it again, I errased the Gemfile.lock and typing bundle again
I had a similar experience.
Here's how I solved it
Display a list of all your local gems for the bundler gem
gem list bundler
N/B: The command above is for rbenv version manager, the one for rvm might be different
This will display the versions of the bundler gem installed locally
bundler (2.1.4, default: 1.17.2)
Note: Your versions might differ from the one here
if you don't have bundler version 2 installed locally, then run
gem install bundler
OR
gem install bundler -v 2.1.4
Note: Replace 2.1.4 with the version you want to install
if you have bundler version 2 already installed locally or just installed it, then you need to simply install an update for RubyGems Package Manager locally. To do this, run
gem update --system
And then finally run
bundle update --bundler
For Docker projects in Ruby on Rails
If you're experiencing this issue when trying to build your application using Docker, simply do this:
Delete the Gemfile.lock file
Please don't create it again by running bundle install.
Run your docker build or docker-compose build command as appropriate to build your project.
This will re-create the Gemfile.lock file and setup the appropriate version of bundler necessary for your project in the Gemfile.lock file.
N/B: As a side note, you can also add this environment variable to your Dockerfile with the Bundler version defined.
ENV BUNDLER_VERSION=2.1.4
A bit late to the party but I just ran into this today as well, and this solution avoids having to uninstall Bundler: just run
heroku buildpacks:set https://github.com/bundler/heroku-buildpack-bundler2
as per discussion on the Bundler issue here.
I had same issue on Local Machine(Development) as-
You must use Bundler 2 or greater with this lockfile.
The issue was with gemfile.lock because my local bundle version and project bundle version was not matching!
Here is solution-
I deleted gemfile.lock
Run the command - bundle install
That solved my problem, it is smooth!
Hope will work for others!
simple gem update bundler did it for me.
I resolved this issue by running gem uninstall bundler to remove 2.0.0.pre.1, renamed the Gemfile.lock file (to remove it from use) and then ran bundle install to reinstall the gemfiles. In my case, I already had access to the earlier bundler version installed by heroku (so when I ran gem uninstall, I was shown all versions available and chose to remove 2.0.0.pre.1).
Even with bundler 2 on the system this error still happens when deploying an app with Ruby 2.6 since Ruby 2.6 ships with a default version of bundler.
If you are using Ruby 2.6 then upgrade to Ruby 2.6.1 to avoid this issue.
The Ruby 2.6.0 is not the case of this problem.
The default version of Bundler incorrectly invoked when using bin stubs.
For more details please refer the following link
Solution:
Bundler 2 is available on the system and is the latest version, So it should be invoked instead of the default bundler version.
Update Rubygems
gem update --system
Update bundler
gem install bundler
Update Gemfile.lock in your project
bundler update --bundler
Yup, so generally uninstalling your version of bundler, removing the gemfile.lock, and finally running gem install bundler -v 1.15.2(which is the version heroku is using) worked.
After that running git push heroku master worked!
For local system
gem install bundler:2.0.0.pre.1
bundle _2.0.0.pre.1_ install
Where "2.0.0.pre.1" is whatever version you need to bundle with.
Don't delete your Gemfile.lock for this, it's there for a reason.
If you're using a docker image like FROM:ruby:2.X.X then you can do the following:
FROM ruby:2.6.2
... # omitted
COPY Gemfile /myapp/Gemfile
COPY Gemfile.lock /myapp/Gemfile.lock
RUN gem uninstall bundler
RUN gem install bundler -v 2.1.4
RUN bundle update --bundler
RUN bundle install
... # omitted
Heroku does not use Bundler 2.0, but 1.15.2, as the tracelog hints.
As far as I am aware, the "workaround" is to create your own buildpack, or simple fork their own:
Open lib/language_pack/ruby.rb in your editor, and change the following line:
BUNDLER_VERSION = "1.11.2"
(README.md at https://github.com/heroku/heroku-buildpack-ruby)
Update: As of Ruby 2.6.1 and Bundler 2.0.1, Heroku now does support Bundler 2.0.1. https://devcenter.heroku.com/articles/bundler-version#known-upgrade-issues
This is not the case for Ruby 2.6.0, as this is incorrectly invoked from binstubs, as #Schneems has mentioned in the comment. He has kindly reported this as a Ruby Bug #15622
For people who are not using Heroku:
I Tried everything and I was still receiving this error. even this link didn't help me: https://github.com/jekyll/jekyll/issues/7463
So this was my solution:
Push your code on GitHub.
delete project folder
create a new folder and pull your code
bundle install
That's it. bundler update --bundler was not helping me at the end and I didn't use it.
One more important thing:
I updated my ruby version but I was getting this error because my RVM default version was an old version.
even when you use rvm use VERSION_NUMBER -- default will not help because as soon as you log out from terminal the default version will change to the old one and you will have the same issue.
For this you can use this answer:
How to set default Ruby version with RVM?
or just uninstall old ruby version with rvm uninstall X.X.X and install the new one with rvm install X.X.X and make it default by rvm use --default X.X.X.
cheers.
I got the same problem for Ruby 2.6.3, nothing listed in answers could help.
The only the following solution worked for me:
bundle update rails
Remove Gemfile.lock
bundle
I had the same issue. In my Gemfile.lock i saw at the end "bundled with bundler 2.0.2", but running bundle --version gave me version 1.17... For me it solved just updateing my bundler with the following command: bundle update --bundler see bundler documentation
I deleted the project and made a git clone from the Heroku app, don´t know if it is a good solution, but it worked for me.
I got the same issue in my local system, my ruby version was low due to which the error was occurring. Fixed it by switching it to updated versions of ruby.
Using bundler 2.0.1 allows for automatic version switching as required by the lock file. In this regard, installing bundler 2.0.1 worked for me.
Installing bundler 2.0.1
gem install bundler -v 2.0.1
Update bundler
bundle update -bundler
I had the same problem today.
In my case the problem was caused by using rvm gemset other than latest I have with ruby 2.7.1 and bundler 2.1.4 (same bundle Gemfile was locked with).
So just take a look at your rvm environment before doing any other solution listed here. Specially if you're running your project on production.
Happy hacks !
Delete gem history and modules installed in rails application.
$ rm -rf vendor/bundle
$ rm Gemfile.lock
and, bundle
$ bundle install --path=vendor/bundle
and, start Rails Server
$ bundle exec rails s
and, connect to browser.
http://localhost:3000/
Same error, but locally.
I finally figured out I was using wrong version of ruby on my command line (I'm using uru to manage ruby versions.)
After all, how could the gemfile use and produce a lock file with version 2.1.4, yet my search didn't find that version!
>gem list bundler
*** LOCAL GEMS ***
bundler (default: 1.16.2, 1.13.1)
capistrano-bundler (1.6.0, 1.1.4)
So I changed to the correct version of ruby and all was good.
Remember, gems are stored with your Ruby version!
I'm pushing code on Heroku as usual.
But this message appear :
Warning: the running version of Bundler (1.15.2) is older than the
version that created the lockfile (1.16.1). We suggest you upgrade to
the latest version of Bundler by running gem install bundler.
So I run:
heroku run gem install bundler
Running gem install bundler on ⬢ myapp... up, run.3401
(Standard-1X)
Fetching: bundler-1.16.1.gem (100%)
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Installing ri documentation for bundler-1.16.1
Done installing documentation for bundler after 11 seconds
1 gem installed
But when I retry to push code:
heroku run bundle install
Running bundle install on ⬢ myapp... up, run.9532 (Standard-1X)
Warning: the running version of Bundler (1.15.2) is older than the
version that created the lockfile (1.16.1). We suggest you upgrade to
the latest version of Bundler by running gem install bundler.
In the gem Gemfile.lock I got:
BUNDLED WITH
1.16.1
I don't understand why this bundler release doesn't want to be install on Heroku.
Bundler 1.15.2 is the version that is pre-installed on Heroku dynos. Changing Bundler to 1.16.1 on your machine doesn't change the version installed on Heroku.
Furthermore, you cannot update Bundler on Heroku by running bundle install. And even if that was possible it would take effect on the next run of Bundler - and usually, you only bundle once on a Heroku dyno.
My advice is: It is just a warning, just ignore it and let's hope that Heroku updates Bundler more ofter in the future.
You also want to make sure you're using a standard Heroku buildpack for this.
When I attempted to upgrade my app from Cedar to Heroku-20, it kept failing with this same bundler error. But, eventually, I remembered that I had install a custom buildback and that turned out to be the source of the incorrect bundler version.
Once I switched back to the default Heroku Ruby buildpack, I was finally able to deploy without any issues.
I'm trying to bundle exec jekyll serve
but I get this error:
Your bundle is locked to addressable (2.5.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of addressable (2.5.0) has removed it. You'll need to update your bundle to a different version of addressable (2.5.0) that hasn't been removed in order to install.
Run `bundle install` to install missing gems.
bundle install gives me
Warning: the running version of Bundler (1.13.6) is older than the version that created the lockfile (1.13.7). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
This works, but it gives me the wrong version I think:
Successfully installed bundler-1.15.1
Parsing documentation for bundler-1.15.1
Done installing documentation for bundler after 4 seconds
1 gem installed
Where is the bundle locked to adressable and what does this mean? I checked my gemfile, it's nothing in there. Can I unlock it? I'm trying to run a boilerplate for jekyll and installed ruby using brew.
The "Your bundle is locked to addressable..." error just means that you have a version of addressable specified in your Gemfile.lock, but it's not installed on your machine (yet). Running bundle install fixes that.
As such, if you run the following, your app should run just fine:
$ bundle install
$ bundle exec jekyll serve
The "Bundler (1.13.6) is older..." warning is just an FYI from the good people at Bundler, encouraging you to upgrade. You can safely ignore it without it affecting your app (but it's good practice to stay up-to-date).
My first problem is a bundler conflict
$ bundle install
Fetching source index from http://rubygems.org/
No compatible versions could be found for required dependencies:
Conflict on: "bundler":
* bundler (0.9.26) activated by bundler (= 0.9.26, runtime)
* bundler (>= 1.0.0.rc.1, runtime) required in Gemfile
All possible versions of origin requirements conflict.
After I figure that out,
Is there anything I need to do to change my Beta 4 Rails app to work on the RC?
You may want to check out upgrading Rails from beta4 to RC. It's mentioning changes to Bundler and to your app's files (like config/* and Rakefile).
There are also important changes to bundler usage (like the default install location is now system-wide, not local). Yehuda gives a great overview of best practices:
Deployment
When deploying, we strongly recommend that you isolate your gems into a local path (using bundle install path --disable-shared-gems). The final version of bundler will come with a --production flag, encapsulating all of the best deployment practices.
For now, please follow the following recommendations (described using Capistrano concepts):
Make sure to always check in a Gemfile.lock that is up to date. This means that after modifying your Gemfile, you should ALWAYS run bundle install.
Symlink the vendor/bundle directory into the application’s shared location (symlink release_path/current/vendor/bundle to release_path/shared/bundled_gems)
Install your bundle by running bundle install vendor/bundle
--disable-shared-gems
For more information, read this blog post.
gem install bundler --pre
bundle install