Your message dated Tue, 7 Jul 2015 14:05:16 -0300
with message-id <[email protected]>
and subject line Re: Bug#791682: Bug in libruby2.1
has caused the Debian Bug report #791682,
regarding Bug in libruby2.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
791682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791682
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libruby2.1
Version: 2.1.5-2+deb8u1
dpkg says libruby2.1 is version 2.1.5, but in
RbConfig::CONFIG['ruby_version'], and in /usr/lib/ruby/2.1.0, it says it is
version 2.1.0.
In /usr/lib/ruby/2.1.0/rubygems/defaults.rb, it is saying that
RbConfig::CONFIG['ruby_version'] is version '2.1.0'.
The problem, looking in '/usr/lib/ruby/2.1.0/rubygems/defaults.rb'. It is
assigning my gempath to: Gem.user_home, '.gem', ruby_engine,
RbConfig::CONFIG['ruby_version'], and RbConfig::CONFIG['ruby_version'] is
equal to '2.1.0
Now. I have ruby 2.1.3, and my gempath is: /home/shawn/.gem/ruby/2.1.3'
because the package 'ruby2.1' is installing to ~/.gem/ruby/2.1.3.
Now why is there a /usr/lib/ruby/2.1.0 on my system saying my ruby version
is '2.1.0', and saying that my gempath is ~/.gem/ruby/2.1.0?
/usr/lib/ruby/2.1.0 is coming from debian package 'libruby2.1', and my
debian package 'ruby2.1' is ruby 2.1.3, and actually installing the gems to
~/.gem/ruby/2.1.3.
uname -r:
> Linux shawnlaptop 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24)
> x86_64 GNU/Linux
>
Let me know if you have any questions, or if I made any mistakes.
Best,
Shawn
--
"Courage, my friends; 'tis not too late to build a better world."
-Tommy Douglas
--- End Message ---
--- Begin Message ---
On Tue, Jul 07, 2015 at 11:21:22AM -0400, Shawn Wallis wrote:
> Package: libruby2.1
>
> Version: 2.1.5-2+deb8u1
>
> dpkg says libruby2.1 is version 2.1.5, but in
> RbConfig::CONFIG['ruby_version'], and in /usr/lib/ruby/2.1.0, it says it is
> version 2.1.0.
>
> In /usr/lib/ruby/2.1.0/rubygems/defaults.rb, it is saying that
> RbConfig::CONFIG['ruby_version'] is version '2.1.0'.
2.1.0 is the API version, and will be 2.1.0 forever.
> The problem, looking in '/usr/lib/ruby/2.1.0/rubygems/defaults.rb'. It is
> assigning my gempath to: Gem.user_home, '.gem', ruby_engine,
> RbConfig::CONFIG['ruby_version'], and RbConfig::CONFIG['ruby_version'] is
> equal to '2.1.0
>
> Now. I have ruby 2.1.3, and my gempath is: /home/shawn/.gem/ruby/2.1.3'
> because the package 'ruby2.1' is installing to ~/.gem/ruby/2.1.3.
Debian does not provide ruby 2.1.3, so this is hardly a problem in
Debian. Ruby itself will always use 2.1.0 regardless of the actual
version, so this looks like a misconfiguration on your part.
> Now why is there a /usr/lib/ruby/2.1.0 on my system saying my ruby version
> is '2.1.0', and saying that my gempath is ~/.gem/ruby/2.1.0?
see above, API version etc.
> /usr/lib/ruby/2.1.0 is coming from debian package 'libruby2.1', and my
> debian package 'ruby2.1' is ruby 2.1.3, and actually installing the gems to
> ~/.gem/ruby/2.1.3.
>
> uname -r:
>
> > Linux shawnlaptop 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24)
> > x86_64 GNU/Linux
> >
>
>
> Let me know if you have any questions, or if I made any mistakes.
you probably have some environment variable (GEM_HOME?) hardcoded, or
you are using some ruby version manager (rvm, rbenv, etc) incorrectly.
This is not a bug in Debian, but if you want help I will need the
output of:
$ ruby -v
$ which ruby
$ which gem
$ gem env
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
