-
-
Notifications
You must be signed in to change notification settings - Fork 548
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
Add possibility to use other releases in debian #383
Conversation
This will allow people to use testing release on Debian 7 where Apache HTTPD 2.4 is available.
Anyone available to review this and merge please ? |
You can use |
When I was testing it, the "package" resource was complaining about it. I'll check again, maybe I missed something.
|
The documentation indicates it should work, so I'd like it if we could figure that out for simplicity's sake. |
@drpebcak Well, even the description of this attribute says: https://docs.chef.io/resource_package.html#properties
And I am pretty sure I was getting an error, as that was the first thing I tried to do without luck. |
@drpebcak ping ? |
@drpebcak here you go:
|
Try it with my fork? I ran through in test-kitchen and it didn't fail... |
@drpebcak Your fork still does the same thing, I don't see any difference. It doesn't matter is it nil, or empty, the package resource still doesn't support "default_release" attribute, which is only supported in apt_package resource even according to the official documentation: https://www.dropbox.com/s/p8fj86mf93p5lam/Screenshot%202015-09-28%2020.02.15.png?dl=0 Take a look here as well: https://github.com/chef/chef/blob/master/lib/chef/resource/apt_package.rb I guess your tests passed because you never set ['apache']['default_release'] to be something other than nil, so the attribute was not applied to the resource because of the if. |
On Ubuntu at least, the compiled version of the
version What version of Chef are you using @ajardan? |
@drpebcak I am using Chef 11.18.12 |
Ah, I get the same error with that old version of chef-client. I'm guessing there was a bug with that version of chef. https://docs.chef.io/release/11-18/resource_package.html#syntax Syntax indicates its for apt packages only, but its shown as used with the package resource directly, not just with apt_package. |
Well, the comment still says:
I'll try with a newer Chef 11 and see how it goes.
|
Right, apt packages only, but it doesn't say 'hey, this only works with the Our test-kitchen suites run with chef 12, so your mileage may vary with chef 11. |
@drpebcak you are right, it works fine with Chef 12.4.3 (in terms of the error I mentioned), but there's a problem in your branch. You have And it should be Want me to do another pull request, or you will fix your branch and merge ? |
Ah, that is important. I'll add that to my fork and then merge it. |
@drpebcak thanks! |
Foodcritic now gives me the following:
|
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. |
This will allow people to use testing release on Debian 7 where Apache HTTPD 2.4 is available.
There are still a lot of servers on Wheezy, and some of them are not that easy to upgrade.
Considering the fact that it is still used, and doesn't have an EOL date yet, we should give an opportunity to those who need this.