[chef] Re: Re: Chef Zero 4.1 Released

[Lamont Granquist < >]

If you're doing gem installs or bundle installs manually then you'll 
need to manually pin ffi-yajl to 1.4.0 one way or another. The upper 
limit for ffi-yajl for chef-zero didn't get bumped so if you've bundled 
or activated 2.0.0 then this version of chef-zero won't load because of 
the pessimistic constraint.

On 4/2/15 7:05 AM, Barthélemy Vessemont wrote:
> It is me or there is many ffi-yajl-2.0.0 conflicts after this upgrade  ?
>
> On Wed, Apr 1, 2015 at 8:02 PM, Daniel DeLeo <
>   
> <mailto:
>  >> wrote:
>
>     Hi Chefs,
>
>     We’ve just released Chef Zero 4.1.0. This release adds support for
>     socketless in-memory requests. Along with a corresponding change
>     to chef-client, this lets you run Chef Client and Knife in local
>     mode without binding to a port—requests get routed directly to
>     Chef Zero in-memory. By default, all requests to the local mode
>     server will use this mechanism, though for compatibility reasons,
>     Chef Zero will still bind to a port by default. To disable
>     networking for the Chef Zero server, you can use the `--no-listen`
>     command line flag or set `listen false` in your config file.
>
>     The Chef Client change is expected to ship in the next feature
>     release of Chef Client (12.3.0). You can follow our progress on
>     the Chef Client portion of the patch here:
>     https://github.com/chef/chef/pull/3160
>
>     Happy Cheffing!
>
>     --
>     Daniel DeLeo
>
>
>
>
>
> --
> Barthélemy Vessemont - 
>
>  
>  
> <mailto:
>  >
> Ingénieur en informatique diplômé de l'UTC (Compiègne)
> Contributeur Chef 
> (
>  )