Skip to content

Instantly share code, notes, and snippets.

@stevenchanin

stevenchanin/shell transcript.md

Last active February 24, 2017 00:12
Show Gist options
  • Save stevenchanin/77db8722018c8721b62e9d40734599f9 to your computer and use it in GitHub Desktop.
Save stevenchanin/77db8722018c8721b62e9d40734599f9 to your computer and use it in GitHub Desktop.
Download ZIP
Trying to do a berks vendor
Raw
shell transcript.md 
steven@ubuntu:~/projects/rails-server-template$ berks vendor
W, [2017-02-23T15:50:00.037000 #1151]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-02-23T15:50:00.037197 #1151]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-02-23T15:50:00.037330 #1151]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-02-23T15:50:00.037456 #1151]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-02-23T15:50:00.069778 #1151]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-02-23T15:50:00.069889 #1151]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
Resolving cookbook dependencies...
Fetching 'nginx' from git://github.com/miketheman/nginx.git (at master)
Git error: command `git reset --hard e36944b0dac1f21044a4f0d01fc566023325cfde` failed. If this error persists, try removing the cache directory at '/home/steven/.berkshelf/.cache/git/a7e1b73c3018df83378b1e5e78affe3e5399e301'.Output from the command:

fatal: Could not parse object 'e36944b0dac1f21044a4f0d01fc566023325cfde'.

  1. I looked through the commits on the nginx.git repo and I don't see that commit has, but there are a lot of commits so I might have missed it.

  2. This is running in a brand new Unbutu 16.04.02 VM

  3. I think the warnings may unrelated & due to some gem version issues with what Chef installs (not sure about this, it's just a guess, but I'd seen some similar warnings when OmniAuth was using an outdated version of Hashie -- omniauth/omniauth#872)

Update

I was looking some more at the nginx repo and I noticed that there was no branch master. There was a 2.7.x and a 3.0.0-rewrite.

So I tried editing the Berksfile and changing:

cookbook 'nginx', github: 'miketheman/nginx'

to

cookbook 'nginx', github: 'miketheman/nginx', branch: '2.7.x'

and then doing a berks update nginx

After that, the berks vendor doesn't crash. (I still get Hashie warnings out the wazoo though...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment