-
Notifications
You must be signed in to change notification settings - Fork 423
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
Running yum update -y can be dangerous #521
Comments
@igorgrin what alternatives are there for resources that introduce new |
So the only way to update a single repo is this hack which should work well in our case. |
@igorgrin please give the tip of |
That does look like a hack... If you add a new repo file to /etc/yum.repos.d/ and then run "yum install yourpackage", it should pull the package from that newly added repo, no? Why do we need to run "yum update" at all? |
For
|
My point was that you must opt in to use The We run We now only update a single repo now and Yum should support version pinning (the lack pf which is the real problem with such accidental updates). |
I removed the |
It looks like in version 5.7 "yum update -y" got introduced.
chef-cookbook/providers/erlang_yum_repository_on_bintray.rb
Line 27 in c5792a4
That line updates every package on the server. That can be dangerous, a single cookbook should not manage the whole system. For example, I got mongodb upgraded to version 4 because I ran rabbitmq recipe after mongodb recipe.
The text was updated successfully, but these errors were encountered: