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

Version bump, conflict with supermarket kafka' #93

Closed
http-418 opened this issue Feb 11, 2016 · 9 comments
Closed

Version bump, conflict with supermarket kafka' #93

http-418 opened this issue Feb 11, 2016 · 9 comments

Comments

@http-418
Copy link
Contributor

In issue #89, Mathias mentioned that he was planning a 1.0.0 release. Unfortunately, the 'kafka' cookbook on chef supermarket is already at version 1.x.x.

Seeing as the supermarket cookbook has already been deprecated by its author, would it be reasonable to bump this kafka cookbook to version 2.0.0, so that specifying depends 'kafka', '~> 2' in a wrapper cookbook cannot possibly resolve to the supermarket-published 'kafka' ?

@mthssdrbrg
Copy link
Contributor

That would be pretty cool, though I don't know much about the Supermarket to be honest, is it possible to "reserve" a name? (I'm guessing not). Or maybe if it would be possible to transfer ownership somehow?

@http-418
Copy link
Contributor Author

It is definitely possible to transfer a name. I'm not sure how much cooperation you will get from the current owner of 'kafka', since he has replaced it with a new cookbook called 'apache_kafka.'

I would like to see the version bump go to '2.0.0' just to avoid accidental resolution of the wrong cookbook by Berkshelf users. It would be better to see Berkshelf throw an error about unavailable versions. Right now it is easy to grab the supermarket version by accident.

@mthssdrbrg
Copy link
Contributor

Cool, I'll reach out to the current owner and to see what's up.

Yeah, think I could live with that, seen the same thing with gems on Rubygems (re: version bump to >= 2.x.y).

@jimdowling
Copy link

Yes, this would be great, as lack of supermarket is a blocker for many installations on firewalled networks that only allow http outgoing access. Supermarket cookbooks work fine with Berkshelf and only outgoing http, but berks-specified github repos are inaccessible, as they use the git protocol to download them.

@mthssdrbrg
Copy link
Contributor

Got the ownership transferred yesterday, and I'll look into releasing v0.9.0 as v2.0.0 on Supermarket this weekend.

@mthssdrbrg
Copy link
Contributor

Just released v2.0.0 to Supermarket. Let me know if there are any problems (I don't use Supermarket myself :)).

@BalasekharNelli12
Copy link

Hi, I am using v2.2.0 [ from Supermarket], it was working good since last week. But, all of sudden, getting the below issue. And cookbook is failing to install.

Recipe: kafka::_configure
* directory[/opt/kafka/config] action create (up to date)
* template[/opt/kafka/config/log4j.properties] action create ==============================================================================
Error executing action create on resource 'template[/opt/kafka/config/log4j.properties]' ==============================================================================
Chef::Mixin::Template::TemplateError
------------------------------------
undefined method `root_logger' for #Mash:0x00000004fc62b0

Thanks

@mthssdrbrg
Copy link
Contributor

@BalasekharNelli12: If you could open a separate issue that'd be great, and please include which version of Chef you're using. Thanks.

@lock
Copy link

lock bot commented Apr 25, 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 Apr 25, 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

No branches or pull requests

4 participants