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

Resolve golang vs chef-golang name conflict via metadata.rb #44

Closed
wants to merge 1 commit into from
Closed

Conversation

nzrgit
Copy link

@nzrgit nzrgit commented Jul 16, 2015

From what I can tell, version 12 of the client wants the name to be the same as the directory. I was unable to upload this cookbook until I changed the name from "golang" to "chef-golang"

The error was:

ERROR: Could not find cookbook chef-golang in your cookbook path, skipping it
ERROR: Failed to upload 1 cookbook.

It is completely possible that this was a config error on my side.

From what I can tell, version 12 of the client wants the name to be the same as the directory. I was unable to upload this cookbook until I changed the name from "golang" to "chef-golang"
@mburns
Copy link
Contributor

mburns commented Sep 27, 2016

I'm 👍 going back to chef-golang as the cookbook name.

Alternatively, @NOX73 could rename this repo to https://github.com/NOX73/golang

This fixes #36

@mburns mburns changed the title Update metadata.rb Resolve golang vs chef-golang name conflict via metadata.rb Sep 30, 2016
@mburns
Copy link
Contributor

mburns commented Feb 25, 2018

fixed in #56

@mburns mburns closed this Feb 25, 2018
@lock
Copy link

lock bot commented Jun 24, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

1 similar comment
@lock
Copy link

lock bot commented Jun 24, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants