| Summary: | app-admin/chef-10.28.0 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | James Cline <lenish> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | alunduil |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
James Cline
2014-04-21 04:10:58 UTC
Just realized when I tested this I had some other custom ebuilds which let ruby20 work for chef's dependencies. Specifically, I added ruby20 to: dev-ruby/mixlib-authentication dev-ruby/mixlib-log dev-ruby/mixlib-config dev-ruby/moneta dev-ruby/rest-client dev-ruby/net-ssh-multi dev-ruby/ohai dev-ruby/ipaddress The ebuilds I am using can all be found at https://github.com/jcline/vagrant-1.5.2-overlay I'm not sure if it's better to make a new bug for each of those, or just use this one? At this point, chef-11 should be the version we try to get stabilized. Especially with 12 coming soon and with it the deprecation of 10. Once 10 is deprecated, I would hope that it would shortly after be removed from the tree. Just my 2¢, ignore me if I'm insane. My thinking was we might have chef-10 in a slot and chef-11 in a slot for people who are still using chef-10 for compatibility reasons. Maybe chef-11 is fully backwards compatible, though? I haven't tried it yet. I mainly did this because I needed to be able to upgrade to vagrant-1.4.2-r2 (the built-in docker plugin is broken on ruby19, it seems), which requires ruby20. This seemed like the quickest way to get chef working with that. vagrant-1.4.3-r2* *** This bug has been marked as a duplicate of bug 505992 *** |