Hi,
I hadn't noticed that. Thanks for pointing it out, and thanks to
Assaf for taking care of it.
Rhett
On Sep 7, 2009, at 9:09 AM, Alex Boisvert wrote:
Just to follow-up in case you didn't notice, this was fixed by Assaf
a week
ago:
commit 712a81c89c4cbb6fff4c37c6279776d39f2adb96
Author: Assaf Arkin <[email protected]>
Date: Sun Aug 30 00:32:53 2009 +0000
Upgraded to RSpec 1.2.8, Net-SSH 2.0.14, jRuby OpenSSL 0.5.2 and
RubyForge 1.0.4
git-svn-id:
https://svn.apache.org/repos/asf/buildr/tr...@80923513f79535-47bb-0310-9956-ffa450edef68
alex
On Fri, Aug 28, 2009 at 12:33 PM, Rhett Sutphin
<[email protected]>wrote:
Hi,
The gemspec in trunk has
spec.add_dependency 'rubyforge', '1.0.3'
spec.add_dependency 'hoe', '~>2.0'
Today, hoe ~>2.0 resolves to hoe 2.3.3. Hoe 2.3.3 has a dependency
on
rubyforge >= 1.0.4. Possible fixes:
- use hoe '~>2.2.0' or '~>2.1.0'
AFAICT, the hoe dependency in buildr is via rspec which requires >=
2.1.0.
- use rubyforge '=1.0.4'
- use rubyforge '~>1.0.0'
I'm doing the third one for the moment, but I don't have a
preference/recommendation other than that.
Rhett
