Thanks for pointing this out Ryan.
After some investigation fixing this will be upgrading fpm. We think that
it will be a risky change to get in to 11.10.0 as we are in the RC stage
and historically we’ve been bitten by fpm version upgrades.
Unless this is a blocking issue for anyone, we are planning to fix this
right after 11.10.0 is released and the fix will be available in the next
version of chef.
Let me know if this sounds good.
On Fri, Jan 31, 2014 at 5:33 PM, Ryan Hass firstname.lastname@example.org wrote:
You might want to look at fixing CHEF-4996 for this release. It’s on the
package building side, so in that sense there shouldn’t be any code
changes required to Chef itself, just the deb which is distributed. It
should be pretty trivial to correct, and was pointed today by a user in
On 01/30/2014 11:12 AM, Serdar Sutay wrote:
We have a release candidate for Chef Client 11.10.0 which we are planning
on shipping next week.
This release has some bug fixes and a lot of contributions from you
can see the full list here:
You can get these releases via omnitruck:
curl -L “https://www.opscode.com/chef/install.sh
https://www.opscode.com/chef/install.sh” | sudo bash -s – -p
Or via rubygems:
gem install chef --pre
Please try them out and let us know if you see any issues.
This electronic message contains information which may be confidential or
privileged. The information is intended for the use of the individual or
entity named above. If you are not the intended recipient, be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited. If you have received this electronic
transmission in error, please notify us by e-mail at (