or Create a profile

Home → Questions →

Update pre released gems

kfl62's Avatar

kfl62

01 Jul, 2010 06:02 AM

Usually I update gems with gem update command, but this ignores gems with pre released versions. Trying with gem update --prerelease I got same results. In conclusion I always check first if a new version exists gem search -r --pre gemname and after I install it with gem install --pre gemname.

Question: Better solution for lazy people :) ?

  1. Support Staff 2 Posted by Nick Quaranto on 05 Jul, 2010 02:41 PM

    Nick Quaranto's Avatar

    Definitely a RubyGems bug. I tend to use gem install all the time but this seems like a valid issue....now that the source is on GItHub you could look into it if you have time before we get to it! :)

    http://github.com/rubygems/rubygems

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

3 people watching.

  • New Issue

  • Conversation Started

    A conversation has been started with the RubyGems.org staff to resolve this discussion.

  • Close the discussion

Recent Discussions

21 May, 2013 11:33 PM Many connectivity errors from production.cf.rubygems.org
04 Aug, 2012 05:46 PM No registration email received
10 Oct, 2012 12:56 AM Can't create a new user account
08 May, 2013 07:56 AM Connection reset while pushing gem

Recent Articles

Supporter FAQ
Gem ownership
Installing gems with no network
Removing a published RubyGem
Why do I get HTTP Response 302 or 301 when installing a gem?