Chad Woolley
Account owner
Chad Woolley's latest activity
Friday, December 12 2008
-
Chad Woolley commented at 10:15 AMThis looks like several errors. The first looks like a connection error - unless for some reason you don't have RubyGems 1.3.1 installed, which had cache errors...
Thursday, December 11 2008
-
Chad Woolley created the ticket at 10:14 AMFrom Steve Conover:
fyi changing that case statement in output_filter.rb from using :'s to then's makes it so gemisntaller runs under 1.9.1
Wednesday, December 10 2008
-
Chad Woolley commented at 11:06 AMYes, but if another gem behaves badly and specifies explicit dependencies when it should not, you can still get these problems.
See these tickets for an example...
-
- State changed from new to invalid
Yes, you can only activate exactly one version of a given gem at a time. You can't activate two different versions.
Wednesday, October 29 2008
-
Chad Woolley commented at 6:05 PMThe (arguable) root cause of this bug is reported here:
http://sod.lighthouseapp.com/pro...
Although there should still be a way to specify gem processing orde...
Saturday, October 25 2008
-
- Tag set to from_rubyforge, high_priority
This is now the default under RubyGems >= 1.3.0, but there are some bugs if you have .gemrc point gemhome and gempath to only ~/.gem, at least on Leopard. See d...
-
Chad Woolley created the ticket at 9:57 AMEither the --config option is not getting passed in all functional tests, or there is a bug in RubyGems.
Monday, October 20 2008
-
Chad Woolley created the ticket at 7:19 PMA few people have asked for this. Maybe some DSL - I've got put some thought into it and have some examples bookmarked and in email.
Feel free to attach any ide...
Monday, October 13 2008
-
Chad Woolley created the ticket at 10:31 PMOtherwise, you can have dependency issues, such as using mislav-will_paginate and rails 2.0.2 with rails > 2.0.2 installed.
See this app to reproduce the error:
...