Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest release contains mac underscore files #239

Open
petracvv opened this issue Nov 5, 2021 · 3 comments
Open

Latest release contains mac underscore files #239

petracvv opened this issue Nov 5, 2021 · 3 comments

Comments

@petracvv
Copy link
Contributor

petracvv commented Nov 5, 2021

This is a similar issue to chef-boneyard/sudo#156

The latest release contains ._ files in the tar archive that is available on supermarket.chef.io. When extracting this archive on a Mac, the BSD tar command there ignores those files when extracting into the cookbook cache causing policyfile checksums to be generated incorrectly. This causes errors when trying to run the policy on machines/OS's that don't ignore the ._* files (such as linux servers you are deploying to).

In this repository I see the following in the extracted tar:

$ find . -name '._*'
./._LICENSE
./resources/._default.rb
./libraries/._matchers.rb
./libraries/._chef_client_updater_helper.rb
./._README.md
./attributes/._default.rb
./recipes/._default.rb
./._chefignore
./._kitchen.dokken.yml

Since this is the second cookbook I've seen with this issue, perhaps there is some bug in your supermarket push procedure?
Either way, those files shouldn't be in the tar release.

The workaround to this is to manually extract the correct version of the cookbook into your policyfile cookbook cache using GNU tar so that the ._* files are extracted as well. Then the checksums will be the same on your machine and any non-Mac machines you are deploying to.

@pdohertybcov
Copy link

I'm also seeing this same error with the latest (3.12.1) release.

@tas50
Copy link
Contributor

tas50 commented Nov 11, 2021

I've released 3.12.2. Let me know if that resolves the problems

@petracvv
Copy link
Contributor Author

I am no longer seeing policyfile errors with the latest version so i think this is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants