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 125287 - unable to specify a particular version at Update
Summary: unable to specify a particular version at Update
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords:
: 125725 137393 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-15 13:37 UTC by Masaki Katakai
Modified: 2008-08-27 13:04 UTC (History)
2 users (show)

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 Masaki Katakai 2008-01-15 13:37:52 UTC
It seems that current Ruby Gems manager does not support to update
to particular version. If install as new, we can specify the version. But
for update, it always will upgrade to the latest version.

Here is a scenario from community member in Japan:

He wants to use Rails 1.2.6 not 2.0.2. But currently when we try to update
Rails on NB6.0, the latest version will be 2.0.2. He could not find a way to
update to 1.2.6 from 1.2.5 on Ruby Gems. (of course, it can be done by gem command)

When we install Rails as new (after deleting 1.2.5), we can specify the
version on UI, but it can not be specified on Gems update.

See http://www.nabble.com/upgrading-to-rails-1.2.6-on-Ruby-Gems-Manager-to14838575.html
Comment 1 Martin Krauskopf 2008-01-15 13:45:36 UTC
Thanks for filing it. Not sure about TM yet, likely after 6.1.
Comment 2 Martin Krauskopf 2008-01-22 12:37:02 UTC
*** Issue 125725 has been marked as a duplicate of this issue. ***
Comment 3 Martin Krauskopf 2008-06-17 09:01:57 UTC
*** Issue 137393 has been marked as a duplicate of this issue. ***
Comment 4 Martin Krauskopf 2008-08-19 20:19:27 UTC
s/enhancement/defect -> clearly defect
Comment 5 Martin Krauskopf 2008-08-27 13:04:30 UTC
This was actually fixed with the new Gem Manager where *all* gems are still listed in 'New Gems' tab so you might
install older version or e.g. reinstall current one. I would leave the default to update to latest and for cases like
your 'New Gems' tab might be used.
Let me know if you disagree.