<qrush>
Still getting Bundler::Fetcher::CertificateFailureError: Could not verify the SSL certificate for https://rubygems.org/. on gem 2.0.0
<drbrain>
jfoy: 1.8 was forked from master a long time ago
<qrush>
Sigh :(
<drbrain>
jfoy: we're not planning on future 1.8 releases
ckrailo has quit [Quit: Computer has gone to sleep.]
<mpapis>
drbrain, whail you are that, should I wait till 2.0.1 before rvm starts installing latest-2.0 ?
<mpapis>
*at that
<drbrain>
mpapis: I plan on releasing RubyGems 2.0.1 tonight
<mpapis>
oh so will it be as default for 1.9.3 / 1.8.7 / rbx / jruby ?
<mpapis>
* be good
<mpapis>
sorry for missing the words
<drbrain>
mpapis: I think so
<mpapis>
great, then I will update when it's out ... just do not forget to do full release ;)
<jfoy>
drbrain: ok, thanks, it just makes it hard for us to take 2.0 until we upgrade more infrastructure because our patches don't apply
<drbrain>
jfoy: 1.8.latest is still a great release
<drbrain>
jfoy: I wouldn't worry about upgrading to rubygems 2 right away, there will probably be another bug fix release while we shake out the minor bugs
tenderlove has joined #rubygems
adkron has quit [Ping timeout: 245 seconds]
qmx|away is now known as qmx
alexkira has quit [Read error: Connection reset by peer]
<huoxito>
drbrain, ah thanks! makes sense I hadn't upgrade to 2.0 yet
<drbrain>
huoxito: I haven't tried personally, but I think 3.2 won't have a problem due to the removed classes in rubygems 2, but earlier rails versions might
<huoxito>
drbrain, I guess I should downgrade then, I still work on 3.0.x project and 3.1.x projects
<drbrain>
huoxito: you can downgrade with gem update --system=old_version
<huoxito>
drbrain, thanks I was looking for that command =)
sn0wb1rd has quit [Quit: sn0wb1rd]
<huoxito>
aah don't remember which was the old version
<huoxito>
I'll get the latest before 2.0
<drbrain>
try 1.8.25
hemanth has joined #rubygems
<huoxito>
That fixed it, my environment is working again, thanks drbrain appreciate it
<drbrain>
excellent
<hemanth>
gem push says : "Can't find 'rubygems-update' in any repo. Check `gem source list`." but the gem source list has the required
<hemanth>
what am I missing?
<drbrain>
hemanth: that check is so you don't push a gem with a prerelease rubygems
<hemanth>
i'm on ruby2.0
<drbrain>
hemanth: can you run with -V
<hemanth>
drbrain, oh :(
<hemanth>
p0
<hemanth>
2.0.0-p0
<drbrain>
hemanth: then it should work, at least, I released rubygems-update-2.0.1 with 2.0.0p0
<drbrain>
hemanth: I'm suspecting a network issue on your end, -V will help confirm
<mpapis>
drbrain, I have fixed tests when the variable is set in environment - I'm not happy with the code, but it works, changes pushed, let me know if it can/should be done better
<drbrain>
mpapis: ok!
<hemanth>
drbrain, no such clues with -V and btw unable to ping to rubygems.org
<drbrain>
mpapis: I probably won't apply it until late next week, I'm going to ruby on ales tomorrow
<drbrain>
hemanth: that's probably your problem
<hemanth>
was able to yank, but not push :(
<drbrain>
maybe you just lost connectivity to it?
<mootpointer>
Man I wish I were able to get to Ruby on Ales.
<hemanth>
able to acess the page from browser
<hemanth>
ICMP is diabled by rubygems.org?
<mpapis>
drbrain, sure, I just got from conference too so I feel your pain :p and now to have some sleep
huoxito has quit [Quit: Leaving]
<drbrain>
hemanth: maybe, since it's on AWS
<hemanth>
drbrain, oh hmm, but if yank worked, why not push on a stable version ...:(
<drbrain>
yes!
<drbrain>
still, -V should show URLs it is accessing
<hemanth>
it just says Upgrading http://rubygems.org/ to HTTPS failed, continuing
<hemanth>
source has both http and https so...
<hemanth>
soruces -r was done
<hemanth>
but also same isse
<hemanth>
but also same issue
<drbrain>
hemanth: maybe it's a bug of 2.0.1 that I missed
<drbrain>
hemanth: can you try downgrading to rubygems 2.0.0?
<drbrain>
gem update --system=2.0.0
abuiles has quit [Ping timeout: 276 seconds]
mockra has quit [Remote host closed the connection]
theartisan has quit [Ping timeout: 252 seconds]
xerxas has quit [Ping timeout: 264 seconds]
mccraig has quit [Ping timeout: 245 seconds]
thbishop has quit [Ping timeout: 264 seconds]
JSharp has quit [Ping timeout: 245 seconds]
kaichanvong has quit [Read error: Operation timed out]
yeban has quit [Ping timeout: 240 seconds]
workmad3 has joined #rubygems
terceiro has joined #rubygems
fidothe has quit [Ping timeout: 245 seconds]
guilleiguaran has quit [Ping timeout: 252 seconds]
jigfox has quit [Quit: jigfox]
hemanth has quit [Read error: Connection reset by peer]
hemanth has joined #rubygems
dsf has joined #rubygems
guilleiguaran has joined #rubygems
vertis has joined #rubygems
hemanth has quit [Ping timeout: 245 seconds]
hemanth has joined #rubygems
<hemanth>
drbrain, still around? sorry was AFK ...downgrading and trying
<justinleitgeb>
Hi folks, I saw the 2.0.2 notice, but I'm only getting 2.0.1 when I do gem update --system... I'm trying to figure out why, but no ideas yet...
<justinleitgeb>
gem update --system 2.0.2 gives "Could not find a valid gem 'rubygems-update' (2.0.2) locally or in a repository"
therealadam has quit [Remote host closed the connection]
adkron_ has joined #rubygems
halogenandtoast has joined #rubygems
<halogenandtoast>
:(
<halogenandtoast>
Fetching source index from https://rubygems.org/ Could not verify the SSL certificate for https://rubygems.org/. There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see bit.ly/ssl-certs. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
<havenwood>
halogenandtoast: What OS? (Just curious.)
<halogenandtoast>
OSX 10.8.2
<halogenandtoast>
seems I need to look into Bundler::Fetcher::CertificateFailureError
envygeeks has joined #rubygems
envygeeks has joined #rubygems
envygeeks has quit [Changing host]
clouder`g has quit [Read error: Connection reset by peer]
<halogenandtoast>
--verbose seems to be failing on