This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 153439 - [65cat] [debug] Unable to install ruby-debug-ide gem during debug launch
Summary: [65cat] [debug] Unable to install ruby-debug-ide gem during debug launch
Status: RESOLVED WORKSFORME
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 07:22 UTC by esmithbss
Modified: 2009-08-26 13:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2008-11-19 07:22:57 UTC
[ BUILD # : RC-2 ]
[ JDK VERSION : 1.6.0_07 ]

When informed by the IDE during debugger startup that the
ruby-debug-ide gem is required for debugging, if ruby is installed
globally and the user chooses to install the proper ruby-debug-ide,
the gem installer requires a root password and does not allow the
user to install the gem locally.
Comment 1 Martin Krauskopf 2008-11-24 17:03:11 UTC
What exactly do you mean by 'locally'? If you set GEM_HOME to user-writable directory, NetBeans should install it
without using sudo. Or do you mena that you would like to choose to which repository to install the gem, when using
multiple RubyGems repositories configuration (GEM_HOME + GEM_PATH)?
Comment 2 esmithbss 2009-03-17 06:57:53 UTC
This bug still exists in 6.5.1.

The problem is that under Ubuntu 8.10, when the system asks for the user to enter an administrative password, the system
takes the password and tries, but always fails.

No matter how carefully you enter the superuser password for the sudo call, NB comes back and says the password is
invalid and therefore, you cannot add the gem to the system.
Comment 3 Martin Krauskopf 2009-08-26 13:45:49 UTC
Hi Eric. I've just tried this and it worked for me (using *root* password). Is this, a bit old issue, still a valid for
you? If not, reopen, thanks.