autogem() fails when run for newly-installed gem
Reported by Chad Woolley | May 20th, 2008 @ 12:30 AM | in 0.5.3 Release
probably need to force rubygems cache refresh
Comments and changes to this ticket
-
John Trupiano March 6th, 2009 @ 01:26 PM
- Tag set to “from_rubyforge, high_priority”
Chad, patch attached. It's a simple one-liner as we discussed. Seems to do the trick for me. In addition to OSX + RubyGems 1.3.1 + 1.8.6-p114, I also verified it works properly on Ubuntu Server 8.04 + RubyGems 1.3.1 + REE (2008-08-08 patchlevel 286).
-John
-
ronin-41535 (at lighthouseapp) July 14th, 2009 @ 09:37 AM
Woot woot! I can verify that this is a problem, and that John's patch fixes it. It would be super-duper to include this in the gem soon, so I don't have to maintain a fork just for this one-line fix.
Cheers!
-
Chad Woolley August 25th, 2009 @ 01:27 AM
- Milestone changed from “1.0 Release” to “0.5.3 Release”
-
Chad Woolley August 25th, 2009 @ 08:17 AM
- State changed from “new” to “open”
-
Chad Woolley August 25th, 2009 @ 04:50 PM
- State changed from “open” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
GemInstaller
http://geminstaller.rubyforge.org
Chad Woolley
John Trupiano