new ffi release 1.13 breaks cookbook

[scalp42]

Hey @tas50

This cookbook relies on https://rubygems.org/gems/ffi-libarchive/versions/1.0.0, which in turns relies on https://rubygems.org/gems/ffi.

Unfortunately, a new release of ffi is out with v1.13.0.

This is now breaking cookbooks as we can't run build_essential resource before somehow due to the gem dependency being in the metadata. It'll complain that it can't natively build ffi 1.13.0.

As the compatibility of this cookbook is restricted to Chef >= 14 (useless with Chef 15), do you know if we could either move the gem dependency to a chef_gem resource (so we can edit_resource and allow whatever custom sauce) or lock the version to the ffi version Chef 14 shipped with (1.12.2)?

Let me know your thoughts, it's a tricky one.

root@default-ubuntu-1804:~# chef-client --version
Chef: 14.15.6
root@default-ubuntu-1804:~# /opt/chef/embedded/bin/gem list | grep -i '^ffi'
ffi (1.12.2)
ffi-yajl (2.3.3)

[scalp42]

Workaround in kitchen for now:

driver:
  name: vagrant
  provision: true
  vagrantfiles:
    - build_essential.rb

Then add a new Vagrantfile called build_essential.rb (Debian family only here):

Vagrant.configure(2) do |config|
  config.vm.provision "shell", inline: <<-SHELL
     sudo apt update
     sudo apt install -y build-essential
  SHELL
end