Red Hat Bugzilla – Bug 250142
How to create package skip list with yum client?
Last modified: 2014-01-21 01:10:27 EST
Description of problem:
Now that up2date has been replaced with yum as a the client tool for manageing
updates, how does one create a package slip list?
With up2date it is handled with the --configure option and specifying a list
like this: "pkgSkipList ['kernel*', 'httpd*', 'mysql*', 'php*']". How to do
the same with yum?
You can add exclude= into the yum.conf file which can do a similar thing.
And then how to override the skip list with yum? With up2date there was:
And, how to force download without install? With up2deate there wass: up2date -
Which could later be followed up with: up2date -fui
Useful functionality which was not replicated in yum?
In order to force update, you can use.
# echo -e "config exclude 0 \n update \n run" | yum -y shell
Note that the former command will not ask for confirmation before installing. To
see what will be installed before running it, remove the -y option
To download without install, you have to install the yum-downloadonly plugin
# yum install yum-downloadonly
Which gives you the --downloadonly option, then
# yum --downloadonly install myPackage
which would down the myPackage package.
Finally if you want to see what's being skipped when doing a "yum update", use
the -d 3 option. e.g.
# yum -d 3 update
Hope that helps
Bob, did Calvin answered your questions?
Additionaly, this is more yum problem, not related to yum-rhn-plugin directly. Changing component to yum.
I think it might be in the 5.2 version, but it's def. in the 5.3/5.4 versions.
Miroslav, Calvin answered my questions.
However, the answers are more complicated than a simple command line flag as was available with up2date. So, this seems more like a kludge than a functionality equivalence.
I theorize a more elegant solution would be to write a series of bash scripts to wrap around the yum, to address the shortfalls when supporting RHEL/RHN. Perhaps using a number of different yum.conf files, one for each functional area would also provide a more robust solution. Just thinking out loud...
FYI - I view this as more of a RHN problem, as up2date is/was for supporting RHEL via RHN.
Thanks for all of the effort.