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.rodrig...@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
> >
>
>
