- From: Daniel DeLeo <
>
- To: chef-dev <
>
- Subject: [chef-dev] Re: ChefDK Windows Status
- Date: Fri, 2 May 2014 09:55:47 -0700
On Friday, May 2, 2014 at 8:17 AM, Daniel DeLeo wrote:
>
Hi Chefs,
>
>
I’ve gotten some interest from people outside Chef-the-company about
>
helping out on ChefDK on windows, so I’d like to share where we’re at in
>
detail.
>
>
The good news is that I’ve been able to get though the build phase
>
successfully. I have these patches either in-flight or merged:
>
>
https://github.com/opscode/omnibus-chef/pull/150
>
https://github.com/opscode/omnibus-software/pull/185
>
https://github.com/opscode/appbundler/pull/3
>
https://github.com/opscode/chef/pull/1399
>
>
The bad news is that Chef’s tests fail because of a segfault triggered by
>
ruby-wmi:
>
>
https://tickets.opscode.com/browse/CHEF-5267
>
>
I should also point out that Chef is currently using a fork of ruby-wmi
>
called rdp-ruby-wmi. I haven’t looked at it too deeply, but it seems that
>
ohai uses features or APIs from this version that are not available in the
>
mainline ruby-wmi 0.4.0. In any case, simply upgrading to the newer
>
mainline version does not resolve the segfault bug.
Quick update, we seem to be making progress with this approach:
https://github.com/opscode/chef/pull/1402
Archive powered by MHonArc 2.6.16.