Hi,
Yes that is the reason. When I executed "bundle" I was getting an error about the current version of bundler being incompatible with the project's version locks.
I have just done "gem uninstal bundler" and now the version being used is 1.17.3 and now I can bundle the project.
thanks for the clarifications.
Joao
On Sun, Jan 17, 2021 at 5:46 PM deivid <deivid.rodriguez@riseup.net <mailto:deivid.rodriguez@riseup.net>> wrote:
Hi!
I would assume that the only way 2.1.4 could've got there is because it was installed through `gem install`, so I guess you could `gem uninstall` it.
That said, I don't have much experience with apt installs of bundler, and how people use them, so take my advice with a grain of salt.
By the way, you said that because of this you can't work on your current project on the machine that has bundler 2.1.4 installed, correct? Why is that? Does it error out because it expects 1.17.3? The reason for this might be that the project has a `Gemfile.lock` file including `BUNDLED WITH 1.17.3`. If this is the case, an alternative is to run `bundle update --bundler` which should update the `Gemfle.lock` file to 2.1.4.
Regard,
David.
El 17/1/21 a las 15:56, Joao Miguel Ferreira escribió:
> Hi David,
>
> Thank you for the clarifications. See more below:
>
> When I run `gem info bundler` I get the following result:
>
> jmf@deb10tp:~$ gem info bundler
> ERROR: While executing gem ... (Gem::CommandLineError)
> Unknown command info
> jmf@deb10tp:~$
>
> additionally I found this:
>
> jmf@deb10tp:~$ gem list | grep bundler
> bundler (2.1.4, 1.17.3)
> jmf@deb10tp:~$
>
> Is there a correct way to safely remove the "2.1.4" thing ?
>
>
> On Sun, Jan 17, 2021 at 12:39 PM deivid <deivid.rodriguez@riseup.net <mailto:deivid.rodriguez@riseup.net> <mailto:deivid.rodriguez@riseup.net <mailto:deivid.rodriguez@riseup.net>>> wrote:
>
> Hello Joao!
>
> Bundler is shipped both as a debian package and as a rubygem, so I think it is likely that you have the debian package installed through apt (which is at version 1.17.3 in your system), and also the rubygem installed through `gem install` (at version 2.1.4).
>
> If you run `gem info bundler`, which result do you get?
>
> Regards,
>
> David.
>
> El 17/1/21 a las 11:31, Joao Miguel Ferreira escribió:
> > Hello all,
> >
> > I'm new to this list and also in ruby, despite using Debian for many years.
> >
> > I have 2 buster machines fully updated. Both have "apt install ruby-bundler". Both show "which bundle" as /usr/bin/bundle. On both the deb version "dpkg -l | grep ruby-bundler" shows 1.17.3
> >
> > but "bundle -v" shows different things. One shows "Bundler version 2.1.4" and the other shows "Bundler version 1.17.3".
> >
> > the consequence of this is that I can work on my current project only on the "1.17.3" machine.
> >
> > Could you help me diagnose this issue ?
> >
> > Thank you
> > João
> >
>