-
Notifications
You must be signed in to change notification settings - Fork 18
Berkshelf 2 compatibility #27
Comments
@motns this is a known issue. I want to get Berkshelf 2.0 stable before I add the integration (I also work on the Berkshelf project). For now, stick with 1.4.5 please |
No problem - thanks! |
Have any idea when it will be considered stable? Currently hitting a bug where berkshelf seems to be pulling in the wrong cookbook from ~/.berkshelf/ into the dir specified by --path. Even though we have the cookbook explicitly locked to a version in metadata.rb. Jamie suggested giving 2.0 and the .lockfile a go. Anyways, hopefully berkshelf 2.0 will be stable enough to get some strainer love. |
@retr0h yes, this is a know issue. But I can't devote time to strainer until I get Berkshelf 2.0 stable. |
Right, which leads to my original question. Are we taking days or weeks? |
@retr0h watch berkshelf, not here, for those kind of updates. As soon as I get Berkshelf stable, I'll update strainer |
Fair enough. Sorry to trouble you for this information. |
Released 3.0, but it's subject to the bugs of BS 2.0 |
Would this be a bug in BS 2.0?
|
3.0.1
|
Works like a champ! Thx for spending your evening releasing this. Very much appreciated. |
Trying to use Berkshelf
2.0.3
alongside Strainer2.1.0
triggers a conflict with the version constraint defined for Berkshelf by Strainer (~> 1.3
).What's strange is that I don't have any problem using Berkshelf
1.4.5
. Any ideas?Also, is there a particular reason why Strainer won't work with a Berkshelf version higher than
1.3
?Thanks, and keep up the good work!
The text was updated successfully, but these errors were encountered: