Debian Bug report logs - #403407
rubygems: gems are installed in /var/lib/gems/X.Y/bin, which is not in $PATH

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Morten Bojsen-Hansen <molsen@ready.dk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: rubygems: gems bin not added to PATH

Date: Sun, 17 Dec 2006 00:06:17 +0100

Package: rubygems
Version: 0.9.0-5
Severity: normal

It seems that this package does not add the gems bin to PATH in
/etc/profiles, which I am quite sure it should. At least it failed to do
so on my system, described below. It should have added
/var/lib/gems/X.Y/bin to PATH.

I realized this when I installed rails via gem and afterwards couldn't
run the 'rails' command. This bug is, of course, not very severe, since
the user is free to add the above-mentioned directory to their PATH, but
it is kind of bothersome, hence the 'normal' severity level.

Best regards,
Morten Bojsen-Hansen

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-rc5
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)

Versions of packages rubygems depends on:
ii  libgems-ruby1.8               0.9.0-5    libraries to use RubyGems, a packa
ii  ruby                          1.8.2-1    An interpreter of object-oriented 

rubygems recommends no packages.

-- no debconf information

Message #10 received at 403407@bugs.debian.org (full text, mbox, reply):

From: Daigo Moriwaki <beatles@sgtpepper.net>

To: 403407@bugs.debian.org

Subject: Re: Bug#403407: rubygems: gems bin not added to PATH

Date: Sun, 27 May 2007 17:29:14 +0900

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Morten

Sorry for the late reply.

Morten Bojsen-Hansen wrote:
> It seems that this package does not add the gems bin to PATH in
> /etc/profiles, which I am quite sure it should. At least it failed to do
> so on my system, described below. It should have added
> /var/lib/gems/X.Y/bin to PATH.

Your request is reasonable. However, there is no standard way in Debian to add
PATH into /etc/profile by other packages than `base-files' which contains that
file. Instead, Users or administrators have to add /var/lib/gems/X.Y/bin to PATH
as I write in /usr/share/doc/libgems-ruby1.8/README.Debian

Executables that come from gems can not be installed /usr/bin because gems are
not Debian packages and may conflict with the Debian packages.

Thanks,
Daigo

- --
Daigo Moriwaki
beatles at sgtpepper dot net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGWUFZNcPj+ukc0lARAsnIAKCCMi3A6eeL26J1ptleCE1ywo/vWQCfVVVn
O0LukturBAkqrNy78diDDqM=
=+4Br
-----END PGP SIGNATURE-----

Message #15 received at 403407@bugs.debian.org (full text, mbox, reply):

From: Renaud Morvan <renaud.morvan@feedback20.com>

To: 403407@bugs.debian.org

Date: Wed, 4 Jul 2007 19:59:39 +0200

There is another issue related to this situation in current stable etch.

Gems bin are located in /var/lib/gems/1.8/bin/ which means that they  
can't be accessed easily with sudo which seems to be compiled with  
secure-path that hardcode PATH env variable

It leads to buggy situation with some popular gems:
	if you install gems like mongrel (as the vast majority of ruby on  
rails users do) you can't start the server under another identity  
than yours without using the full path. Can't start the provided  
init.d script for mongrel cluster ...
	And "normal user" that don't know about the sudo security stuff just  
get "command not found" => headache

As long as this package will ghetto the gems bin in some exotic  
folder, I fear that compiling rubygems will remains mainstream as  
it's not worst than symlinking to /usr/local/bin :/

I understand that the scope of this situation is wider than that,  
that's much more about the compatibility between gems and apt-get

Hope that one day I'll be able to be an happy debian rubyist :)

Message #20 received at 403407@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Renaud Morvan <renaud.morvan@feedback20.com>

Cc: 403407@bugs.debian.org, control@bugs.debian.org

Subject: Re: your mail

Date: Wed, 5 Sep 2007 13:35:23 +0200

retitle 403407 rubygems: gems are installed in /var/lib/gems/X.Y/bin, which is not in $PATH
severity 403407 wishlist
tags 403407 + wontfix
thanks

On 04/07/07 at 19:59 +0200, Renaud Morvan wrote:
> There is another issue related to this situation in current stable etch.
>
> Gems bin are located in /var/lib/gems/1.8/bin/ which means that they can't 
> be accessed easily with sudo which seems to be compiled with secure-path 
> that hardcode PATH env variable
>
> It leads to buggy situation with some popular gems:
> 	if you install gems like mongrel (as the vast majority of ruby on rails 
> users do) you can't start the server under another identity than yours 
> without using the full path. Can't start the provided init.d script for 
> mongrel cluster ...
> 	And "normal user" that don't know about the sudo security stuff just get 
> "command not found" => headache
>
> As long as this package will ghetto the gems bin in some exotic folder, I 
> fear that compiling rubygems will remains mainstream as it's not worst than 
> symlinking to /usr/local/bin :/
>
> I understand that the scope of this situation is wider than that, that's 
> much more about the compatibility between gems and apt-get
>
> Hope that one day I'll be able to be an happy debian rubyist :)

yeah, all of this sucks, really. The problem is that the upstream
rubygems developers don't care, and that it's impossible to change that
without their cooperation. I know it's frustrating.

Note that this issue is documented in
/usr/share/doc/rubygems/README.Debian
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #33 received at 403407@bugs.debian.org (full text, mbox, reply):

From: "Joseph Method" <tristil@gmail.com>

To: 403407@bugs.debian.org

Subject: Request for comment

Date: Thu, 25 Sep 2008 12:21:13 -0400

[Message part 1 (text/plain, inline)]

Can we reconsider the status of this ticket in light of the proposal on
https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/145267 ?

As I understand it, Neil Wilson patches Rubygems to link files into
/usr/local/bin and uses the alternatives system to decide whether to load
ruby1.9 or ruby1.8 gems (I may not understand this part). Many objections
were raised about creating divergence between Debian and Ubuntu, and also an
objection was raised about using alternatives as a Debian-only tool. There
was also a complaint about the use of patching tool.

Virtues of Neil Wilson's approach are that it avoids adding
/var/rubygems/bin to the $PATH (by far the easiest approach IMO; I don't
quite understand the objections myself). I can help with cleaning up his
patch if his is considered a sound approach.
-- 
-J. Method

[Message part 2 (text/html, inline)]

Message #38 received at 403407@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Joseph Method <tristil@gmail.com>, 403407@bugs.debian.org

Subject: Re: [DRE-maint] Bug#403407: Request for comment

Date: Fri, 26 Sep 2008 09:03:27 +0200

On 25/09/08 at 12:21 -0400, Joseph Method wrote:
> Can we reconsider the status of this ticket in light of the proposal on
> https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/145267 ?
> 
> As I understand it, Neil Wilson patches Rubygems to link files into
> /usr/local/bin and uses the alternatives system to decide whether to load
> ruby1.9 or ruby1.8 gems (I may not understand this part). Many objections
> were raised about creating divergence between Debian and Ubuntu, and also an
> objection was raised about using alternatives as a Debian-only tool. There
> was also a complaint about the use of patching tool.
> 
> Virtues of Neil Wilson's approach are that it avoids adding
> /var/rubygems/bin to the $PATH (by far the easiest approach IMO; I don't
> quite understand the objections myself). I can help with cleaning up his
> patch if his is considered a sound approach.

I think that we should just install the binary wrappers to
/usr/local/bin instead of /var/.../1.{8,9}/bin. That's what rubygems
upstream does anyway (or almost does, I think it installs to /usr/bin).
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #43 received at 403407-close@bugs.debian.org (full text, mbox, reply):

From: Daigo Moriwaki <daigo@debian.org>

To: 403407-close@bugs.debian.org

Subject: Bug#403407: fixed in rubygems 1.7.2-1

Date: Fri, 29 Apr 2011 16:19:31 +0000

Source: rubygems
Source-Version: 1.7.2-1

We believe that the bug you reported is fixed in the latest version of
rubygems, which is due to be installed in the Debian FTP archive:

rubygems-doc_1.7.2-1_all.deb
  to main/r/rubygems/rubygems-doc_1.7.2-1_all.deb
rubygems1.8_1.7.2-1_all.deb
  to main/r/rubygems/rubygems1.8_1.7.2-1_all.deb
rubygems_1.7.2-1.debian.tar.gz
  to main/r/rubygems/rubygems_1.7.2-1.debian.tar.gz
rubygems_1.7.2-1.dsc
  to main/r/rubygems/rubygems_1.7.2-1.dsc
rubygems_1.7.2-1_all.deb
  to main/r/rubygems/rubygems_1.7.2-1_all.deb
rubygems_1.7.2.orig.tar.gz
  to main/r/rubygems/rubygems_1.7.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 403407@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daigo Moriwaki <daigo@debian.org> (supplier of updated rubygems package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 29 Apr 2011 19:07:08 +0900
Source: rubygems
Binary: rubygems rubygems1.8 rubygems-doc
Architecture: source all
Version: 1.7.2-1
Distribution: unstable
Urgency: low
Maintainer: Daigo Moriwaki <daigo@debian.org>
Changed-By: Daigo Moriwaki <daigo@debian.org>
Description: 
 rubygems   - package management framework for Ruby libraries/applications
 rubygems-doc - Transitional package for rubygems
 rubygems1.8 - Transitional package for rubygems
Closes: 403407 448639
Changes: 
 rubygems (1.7.2-1) unstable; urgency=low
 .
   [ Lucas Nussbaum ]
   * New upstream release.
   * Switch to gem2deb-based packaging. Rename source and binary packages.
   * Drop 50_add_missing_require_yaml.diff: fixed upstream.
   * Change 01_default_gem_path.diff:
     + executables are now installed to /usr/local/bin.
     + but the other files created by rubygems stay in /var/lib/gems/1.8.
     Several commenters in #448639 and #403407 argued in favor of the switch to
     /usr/local/bin. Those two bugs can therefore be closed. However, the issue
     is not completely solved, as rubygems still installs files in /var/lib/gems.
     Nobody in the bug logs explained why that was an issue. If you care about
     it, please open a new bug. Closes: #448639, #403407
   * Add disable-failing-tests.diff: disable tests that are failing due to
     Debian-specific changes to rubygems.
 .
   [ Daigo Moriwaki ]
   * Switched the build framework from cdbs to dh. (thanks to Lucas)
Checksums-Sha1: 
 b4f5a7a4f44aab1b0d89a1293052a0ebd00893b6 1410 rubygems_1.7.2-1.dsc
 d878ae52f40eb71e59708afc57303172f0327fad 245606 rubygems_1.7.2.orig.tar.gz
 39fb260e11da629bc4463be0e763806c97279ff3 24086 rubygems_1.7.2-1.debian.tar.gz
 f20eb7b0aab2691817d0dd70c354778873b00b15 446258 rubygems_1.7.2-1_all.deb
 107d594cee8f7a707b499d3bc09fedbd5154de0b 24734 rubygems1.8_1.7.2-1_all.deb
 1d65743cd2aca1c2948bd5d1e1c29f3a251bbf2d 24738 rubygems-doc_1.7.2-1_all.deb
Checksums-Sha256: 
 0db30e9d6cc6fb7b5c5ee0b5b1f15da28886c2d1a1fcc68c776623431d1a63a1 1410 rubygems_1.7.2-1.dsc
 28c6969d48e2ec0d9df6ccd7c73d46d9b0c115ca6acb34f091b39a3e9049692c 245606 rubygems_1.7.2.orig.tar.gz
 3c8106d4104646e12c904846100e5bc03f57a0df4a68a50925d96ba47d28e93a 24086 rubygems_1.7.2-1.debian.tar.gz
 8ed057610ecf416d7ce25d80260d83b8e815749a7a72b498d7c8cb2bffb68498 446258 rubygems_1.7.2-1_all.deb
 bf31dcd2d22e9c84329a296899c6fdade707ced0800171b97957a7dd8f25b18b 24734 rubygems1.8_1.7.2-1_all.deb
 cb587fdaf6b7e415c12859736534a5107d584dc12d95a4a2fbe35093ba21b532 24738 rubygems-doc_1.7.2-1_all.deb
Files: 
 bcfd65ffc62acf51b41dd3193c19c2c1 1410 ruby optional rubygems_1.7.2-1.dsc
 8d67d0bc44b0317dc37e200dcf6627ea 245606 ruby optional rubygems_1.7.2.orig.tar.gz
 1464f1f2988b8d0a222a70c140c93497 24086 ruby optional rubygems_1.7.2-1.debian.tar.gz
 b84c9c97299baedec1d792ae30cd51c5 446258 ruby optional rubygems_1.7.2-1_all.deb
 4afdcc8ed28ee6d959defa36b396c33a 24734 oldlibs optional rubygems1.8_1.7.2-1_all.deb
 6b0945175c5daae9c4fe2b243dff8912 24738 oldlibs optional rubygems-doc_1.7.2-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk264PEACgkQNcPj+ukc0lAzqACgvGqAq8geb9+FAGbVK+4Gnlci
aWYAoJgBmOXuzIKgIQq85DEs8aO7ZmMb
=YLOY
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.