summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CHANGELOG.md2
-rw-r--r--RELEASE_NOTES.md22
2 files changed, 24 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f91d4a722b..e90b2bc35d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -21,6 +21,8 @@
[pr#3594](https://github.com/chef/chef/pull/3594): Update service provider for OSX 10.11
* [**Nate Walck**](https://github.com/natewalck):
[pr#3704](https://github.com/chef/chef/pull/3704): Add SIP (OS X 10.11) support
+
+* [pr#3774](https://github.com/chef/chef/pull/3774) Add support for yum-deprecated in yum provider
* [pr#3793](https://github.com/chef/chef/pull/3793) CHEF-5372: Support specific `run_levels` for RedHat service
* [pr#2460](https://github.com/chef/chef/pull/2460) add privacy flag
* [pr#1259](https://github.com/chef/chef/pull/1259) CHEF-5012: add methods for template breadcrumbs
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 78daac899e..a1d4bfad14 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,2 +1,24 @@
# Chef Client Release Notes 12.5.0:
* OSX 10.11 support (support for SIP and service changes)
+
+## Support for `/usr/bin/yum-deprecated` in the yum provider
+
+In Fedora 22 yum has been deprecated in favor of DNF. Unfortunately, while DNF tries to be backwards
+compatible with yum, the yum provider in Chef is not compatible with DNF. Until a proper `dnf_package`
+resource and associated provider is written and merged into core, 12.5.0 has been patched so that the
+`yum_package` resource takes a property named `yum_binary` which can be set to point at the yum binary
+to run for all its commands. The `yum_binary` will also default to `yum-deprecated` if the
+`/usr/bin/yum-deprecated` command is found on the system. This means that Fedora 22 users can run
+something like this early in their chef-client run:
+
+```ruby
+if File.exist?("/usr/bin/dnf")
+ execute "dnf install -y yum" do
+ not_if { File.exist?("/usr/bin/yum-deprecated") }
+ end
+end
+```
+
+After which the yum-deprecated binary will exist, and the yum provider will find it and should operate
+normally and successfully.
+