1yum(8) yum(8)
2
6 yum - Yellowdog Updater Modified
7
9 yum [options] [command] [package ...]
10
12 yum is an interactive, rpm based, package manager. It can automatically
13 perform system updates, including dependency analysis and obsolete pro‐
14 cessing based on "repository" metadata. It can also perform installa‐
15 tion of new packages, removal of old packages and perform queries on
16 the installed and/or available packages among many other commands/ser‐
17 vices (see below). yum is similar to other high level package managers
18 like apt-get and smart.
19 While there are some graphical interfaces directly to the yum code,
21 more recent graphical interface development is happening with Pack‐
22 ageKit and the gnome-packagekit application.
23 command is one of:
25 * install package1 [package2] [...]
26 * update [package1] [package2] [...]
27 * update-to [package1] [package2] [...]
28 * update-minimal [package1] [package2] [...]
29 * check-update
30 * upgrade [package1] [package2] [...]
31 * upgrade-to [package1] [package2] [...]
32 * distribution-synchronization [package1] [package2] [...]
33 * remove | erase package1 [package2] [...]
34 * autoremove [package1] [...]
35 * list [...]
36 * info [...]
37 * provides | whatprovides feature1 [feature2] [...]
38 * clean [ packages | metadata | expire-cache | rpmdb | plugins | all ]
39 * makecache [fast]
40 * groups [...]
41 * search string1 [string2] [...]
42 * shell [filename]
43 * resolvedep dep1 [dep2] [...]
44 (maintained for legacy reasons only - use repoquery or yum pro‐
45 vides)
46 * localinstall rpmfile1 [rpmfile2] [...]
47 (maintained for legacy reasons only - use install)
48 * localupdate rpmfile1 [rpmfile2] [...]
49 (maintained for legacy reasons only - use update)
50 * reinstall package1 [package2] [...]
51 * downgrade package1 [package2] [...]
52 * deplist package1 [package2] [...]
53 * repolist [all|enabled|disabled]
54 * repoinfo [all|enabled|disabled]
55 * repository-packages <enabled-repoid> <install|remove|remove-or-rein‐
56 stall|remove-or-distribution-synchronization> [package2] [...]
57 * version [ all | installed | available | group-* | nogroups* | grou‐
58 plist | groupinfo ]
59 * history [info|list|packages-list|packages-info|summary|addon-
60 info|redo|undo|rollback|new|sync|stats]
61 * load-transaction [txfile]
62 * updateinfo [summary | list | info | remove-pkgs-ts | exclude-updates
63 | exclude-all | check-running-kernel]
64 * fssnapshot [summary | list | have-space | create | delete]
65 * fs [filters | refilter | refilter-cleanup | du]
66 * check
67 * help [command]
68 Unless the --help or -h option is given, one of the above commands must
70 be present.
71 Repository configuration is honored in all operations.
73 install
75 Is used to install the latest version of a package or group of
76 packages while ensuring that all dependencies are satisfied.
77 (See Specifying package names for more information) If no pack‐
78 age matches the given package name(s), they are assumed to be a
79 shell glob and any matches are then installed. If the name
80 starts with @^ then it is treated as an environment group (group
81 install @^foo), an @ character and it's treated as a group
82 (plain group install).
83 If the name starts with a "-" character, then a search is done
85 within the transaction and any matches are removed. Note that
86 Yum options use the same syntax and it may be necessary to use
87 "--" to resolve any possible conflicts.
88 If the name is a file, then install works like localinstall. If
90 the name doesn't match a package, then package "provides" are
91 searched (e.g. "_sqlitecache.so()(64bit)") as are filelists (Eg.
92 "/usr/bin/yum"). Also note that for filelists, wildcards will
93 match multiple packages.
94 Because install does a lot of work to make it as easy as possi‐
96 ble to use, there are also a few specific install commands
97 "install-n", "install-na" and "install-nevra". These only work
98 on package names, and do not process wildcards etc.
99 update If run without any packages, update will update every currently
101 installed package. If one or more packages or package globs are
102 specified, Yum will only update the listed packages. While
103 updating packages, yum will ensure that all dependencies are
104 satisfied. (See Specifying package names for more information)
105 If the packages or globs specified match to packages which are
106 not currently installed then update will not install them.
107 update operates on groups, files, provides and filelists just
108 like the "install" command.
109 If the main obsoletes configure option is true (default) or the
111 --obsoletes flag is present yum will include package obsoletes
112 in its calculations - this makes it better for distro-version
113 changes, for example: upgrading from somelinux 8.0 to somelinux
114 9.
115 Note that "update" works on installed packages first, and only
117 if there are no matches does it look for available packages. The
118 difference is most noticeable when you do "update foo-1-2" which
119 will act exactly as "update foo" if foo-1-2 is installed. You
120 can use the "update-to" if you'd prefer that nothing happen in
121 the above case.
122 update-to
124 This command works like "update" but always specifies the ver‐
125 sion of the package we want to update to.
126 update-minimal
128 This works like the update command, but if you have the package
129 foo-1 installed and have foo-2 (bugfix) and foo-3 (enhancement)
130 available with updateinfo.xml then update-minimal --bugfix will
131 update you to foo-2.
132 check-update
134 Implemented so you could know if your machine had any updates
135 that needed to be applied without running it interactively.
136 Returns exit value of 100 if there are packages available for an
137 update. Also returns a list of the packages to be updated in
138 list format. Returns 0 if no packages are available for update.
139 Returns 1 if an error occurred. Running in verbose mode also
140 shows obsoletes.
141 upgrade
143 Is the same as the update command with the --obsoletes flag set.
144 See update for more details.
145 upgrade-to
147 This command works like "upgrade" but always specifies the ver‐
148 sion of the package we want to update to.
149 distribution-synchronization or distro-sync
151 Synchronizes the installed package set with the latest packages
152 available, this is done by either obsoleting, upgrading or down‐
153 grading as appropriate. This will "normally" do the same thing
154 as the upgrade command however if you have the package FOO
155 installed at version 4, and the latest available is only version
156 3, then this command will downgrade FOO to version 3.
157 If you give the optional argument "full", then the command will
159 also reinstall packages where the install checksum and the
160 available checksum do not match. And remove old packages (can be
161 used to sync. rpmdb versions). The optional argument "different"
162 can be used to specify the default operation.
163 This command does not perform operations on groups, local pack‐
165 ages or negative selections.
166 remove or erase
168 Are used to remove the specified packages from the system as
169 well as removing any packages which depend on the package being
170 removed. remove operates on groups, files, provides and
171 filelists just like the "install" command.(See Specifying pack‐
172 age names for more information)
173 Note that "yum" is included in the protected_packages configura‐
175 tion, by default. So you can't accidentally remove yum itself.
176 The remove_leaf_only configuration changes the behaviour of this
178 command to only remove packages which aren't required by some‐
179 thing else.
180 The clean_requirements_on_remove configuration changes the be‐
182 haviour of this command to also remove packages that are only
183 dependencies of this package.
184 Because remove does a lot of work to make it as easy as possible
186 to use, there are also a few specific remove commands "remove-
187 n", "remove-na" and "remove-nevra". These only work on package
188 names, and do not process wildcards etc.
189 autoremove
191 With one or more arguments this command works like running the
193 "remove" command with the clean_requirements_on_remove turned
194 on. However you can also specify no arguments, at which point it
195 tries to remove any packages that weren't installed explicitly
196 by the user and which aren't required by anything (so called
197 leaf packages).
198 Because autoremove does a lot of work to make it as easy as pos‐
200 sible to use, there are also a few specific autoremove commands
201 "autoremove-n", "autoremove-na" and "autoremove-nevra". These
202 only work on package names, and do not process wildcards etc.
203 list Is used to list various information about available packages;
205 more complete details are available in the List Options section
206 below.
207 provides or whatprovides
209 Is used to find out which package provides some feature or file.
210 Just use a specific name or a file-glob-syntax wildcards to list
211 the packages available or installed that provide that feature or
212 file.
213 search This is used to find packages when you know something about the
215 package but aren't sure of it's name. By default search will try
216 searching just package names and summaries, but if that "fails"
217 it will then try descriptions and url.
218 Yum search orders the results so that those packages matching
220 more terms will appear first.
221 You can force searching everything by specifying "all" as the
223 first argument.
224 info Is used to list a description and summary information about
226 available packages; takes the same arguments as in the List
227 Options section below.
228 clean Is used to clean up various things which accumulate in the yum
230 cache directory over time. More complete details can be found
231 in the Clean Options section below.
232 makecache
234 Is used to download and make usable all the metadata for the
235 currently enabled yum repos. If the argument "fast" is passed,
236 then we just try to make sure the repos. are current (much like
237 "yum clean expire-cache").
238 groups A command, new in 3.4.2, that collects all the subcommands that
240 act on groups together. Note that recent yum using distributions
241 (Fedora-19+, RHEL-7+) have configured group_command=objects
242 which changes how group commands act in some important ways.
243 "group install" is used to install all of the individual pack‐
245 ages in a group, of the specified types (this works as if you'd
246 taken each of those package names and put them on the command
247 line for a "yum install" command).
248 The group_package_types configuration option specifies which
249 types will be installed.
250 If you wish to "reinstall" a group so that you get a package
251 that is currently blacklisted the easiest way to do that cur‐
252 rently is to install the package manually and then run "groups
253 mark packages-sync mygroup mypackagename" (or use yumdb to set
254 the group_member of the package(s)).
255 "group update" is just an alias for group install, when using
257 group_command=compat. This will install packages in the group
258 not already installed and upgrade existing packages. With
259 group_command=simple it will just upgrade already installed
260 packages. With group_command=objects it will try to upgrade the
261 group object, installing any available packages not blacklisted
262 (marked '-' in group info) and will upgrade the installed pack‐
263 ages.
264 "group list" is used to list the available groups from all yum
266 repos. When group_command=objects the group is installed if the
267 user explicitly installed it (or used the group mark* commands
268 to mark it installed). It does not need to have any packages
269 installed. When not using group_command=objects groups are
270 shown as "installed" if all mandatory packages are installed, or
271 if a group doesn't have any mandatory packages then it is
272 installed if any of the optional or default package are
273 installed (when not in group_command=objects mode). You can
274 pass optional arguments to the list/summary commands: installed,
275 available, environment, language, packages, hidden and ids (or
276 any of those prefixed by "no" to turn them off again). If you
277 pass the -v option, to enable verbose mode, then the groupids
278 are displayed by default (but "yum group list ids" is often eas‐
279 ier to read).
280 "group remove" is used to remove all of the packages in a group,
282 unlike "groupinstall" this will remove everything regardless of
283 group_package_types. It is worth pointing out that packages can
284 be in more than one group, so "group install X Y" followed by
285 "group remove Y" does not do give you the same result as "group
286 install X".
287 The groupremove_leaf_only configuration changes the behaviour of
289 this command to only remove packages which aren't required by
290 something else.
291 "group info" is used to give the description and package list of
293 a group (and which type those packages are marked as). Note that
294 you can use the yum-filter-data and yum-list-data plugins to
295 get/use the data the other way around (i.e. what groups own
296 packages need updating). If you pass the -v option, to enable
297 verbose mode, then the package names are matched against
298 installed/available packages similar to the list command.
299 When using group_command=objects, the info command will display
301 markers next to each package saying how that package relates to
302 the group object. The meaning of these markers is:
303 "-" = Package isn't installed, and won't be installed as part of
305 the group (Eg. "yum group install foo -pkgA" or "yum group
306 install foo; yum remove pkgA" … this will have pkgA marked as
307 '-')
308 "+" = Package isn't installed, but will be the next time you run
309 "yum upgrade" or "yum group upgrade foo"
310 " " = Package is installed, but wasn't installed via the group
311 (so "group remove foo" won't remove it).
312 "=" = Package is installed, and was installed via the group.
313 you can move an installed package into an installed group using
315 either "group mark package-sync/package-sync-forced" or "yumdb
316 set group_member".
317 "group summary" is used to give a quick summary of how many
319 groups are installed and available.
320 "group mark" and "group unmark" are used when groups are config‐
322 ured in group_command=objects mode. These commands then allow
323 you to alter yum's idea of which groups are installed, and the
324 packages that belong to them.
325 "group mark install" mark the group as installed. When installed
327 "yum upgrade" and "yum group upgrade" will install new packages
328 for the group (only those packages already installed will be
329 marked as members of the installed group to start with).
330 "group mark remove" the opposite of mark install.
332 "group mark packages" takes a group id (which must be installed)
334 and marks any given installed packages (which aren't members of
335 a group) as members of the group. Note that the data from the
336 repositories does not need to specify the packages as a member
337 of the group.
338 "group mark packages-force" works like mark packages, but
340 doesn't care if the packages are already members of another
341 group.
342 "group mark blacklist" will blacklist all packages marked to be
344 installed for a group. After this command a "yum group upgrade"
345 will not install any new packages as part of the group.
346 "group mark convert-blacklist"
348 "group mark convert-whitelist"
350 "group mark convert" converts the automatic data you get without
352 using groups as objects into groups as objects data, in other
353 words this will make "yum --setopt=group_command=objects groups
354 list" look as similar as possible to the current output of "yum
355 --setopt=group_command=simple groups list". This makes it much
356 easier to convert to groups as objects without having to rein‐
357 stall. For groups that are installed the whitelist variant will
358 mark all uninstalled packages for the group as to be installed
359 on the next "yum group upgrade", the blacklist variant (current
360 default) will mark them all as blacklisted.
361 "group unmark packages" remove a package as a member from any
363 groups.
364 shell Is used to enter the 'yum shell', when a filename is specified
366 the contents of that file is executed in yum shell mode. See
367 yum-shell(8) for more info.
368 resolvedep
370 Is used to list packages providing the specified dependencies,
371 at most one package is listed per dependency. This command is
372 maintained for legacy reasons only, use repoquery instead.
373 localinstall
375 Is used to install a set of local rpm files. If required the
376 enabled repositories will be used to resolve dependencies. Note
377 that the install command will do a local install, if given a
378 filename. This command is maintained for legacy reasons only.
379 localupdate
381 Is used to update the system by specifying local rpm files. Only
382 the specified rpm files of which an older version is already
383 installed will be installed, the remaining specified packages
384 will be ignored. If required the enabled repositories will be
385 used to resolve dependencies. Note that the update command will
386 do a local update, if given a filename. This command is main‐
387 tained for legacy reasons only.
388 reinstall
390 Will reinstall the identically versioned package as is currently
391 installed. This does not work for "installonly" packages, like
392 Kernels. reinstall operates on groups, files, provides and
393 filelists just like the "install" command.
394 downgrade
396 Will try and downgrade a package from the version currently
397 installed to the previously highest version (or the specified
398 version). The depsolver will not necessarily work, but if you
399 specify all the packages it should work (thus, all the simple
400 cases will work). Also this does not work for "installonly"
401 packages, like Kernels. downgrade operates on groups, files,
402 provides, filelists and rpm files just like the "install" com‐
403 mand.
404 swap At it's simplest this is just a simpler way to remove one set of
406 package(s) and install another set of package(s) without having
407 to use the "shell" command. However you can specify different
408 commands to call than just remove or install, and you can list
409 multiple packages (it splits using the "--" marker). Note that
410 option parsing will remove the first "--" in an argument list on
411 the command line.
412 Examples:
415 swap foo bar
417 swap -- remove foo -- install bar
418 swap foo group install bar-grp
419 swap -- group remove foo-grp -- group install bar-grp
420 deplist
422 Produces a list of all dependencies and what packages provide
423 those dependencies for the given packages. As of 3.2.30 it now
424 just shows the latest version of each package that matches (this
425 can be changed by using --showduplicates) and it only shows the
426 newest providers (which can be changed by using --verbose).
427 repolist
429 Produces a list of configured repositories. The default is to
430 list all enabled repositories. If you pass -v, for verbose mode,
431 or use repoinfo then more information is listed. If the first
432 argument is ´enabled´, ´disabled´ or ´all´ then the command will
433 list those types of repos.
434 You can pass repo id or name arguments, or wildcards which to
436 match against both of those. However if the id or name matches
437 exactly then the repo will be listed even if you are listing
438 enabled repos. and it is disabled.
439 In non-verbose mode the first column will start with a ´*´ if
441 the repo. has metalink data and the latest metadata is not local
442 and will start with a ´!´ if the repo. has metadata that is
443 expired (this can happen due to metadata_expire_filter). For
444 non-verbose mode the last column will also display the number of
445 packages in the repo. and (if there are any user specified
446 excludes) the number of packages excluded.
447 One last special feature of repolist, is that if you are in non-
449 verbose mode then yum will ignore any repo errors and output the
450 information it can get (Eg. "yum clean all; yum -C repolist"
451 will output something, although the package counts/etc. will be
452 zeroed out).
453 repoinfo
455 This command works exactly like repolist -v.
457 repository-packages
459 Treat a repo. as a collection of packages (like "yum groups")
460 allowing the user to install or remove them as a single entity.
461 "repository-packages <repo> list" - Works like the "yum list"
463 command, but only shows packages from the given repository.
464 "repository-packages <repo> info" - Works like the "yum info"
466 command, but only shows packages from the given repository.
467 "repository-packages <repo> check-update" - Works like the "yum
469 check-update" command, but only shows packages from the given
470 repository.
471 "repository-packages <repo> install" - Install all of the pack‐
473 ages in the repository, basically the same as: yum install
474 $(repoquery --repoid=<repo> -a). Specific packages/wildcards
475 can be specified.
476 "repository-packages <repo> upgrade" - Update all of the pack‐
478 ages in the repository, basically the same as: yum upgrade
479 $(repoquery --repoid=<repo> -a). Specific packages/wildcards
480 can be specified.
481 "repository-packages <repo> upgrade-to" - Update all of the
483 packages in the repository, basically the same as: yum upgrade
484 $(repoquery --repoid=<repo> -a). Without arguments it works the
485 same as upgrade, with arguments it just interprets them as the
486 versions you want to move to.
487 "repository-packages <repo> reinstall-old" - ReInstall all of
489 the packages that are installed from the repository and avail‐
490 able in the repository, similar to: yum reinstall $(yumdb
491 search-quiet from_repo <repo>).
492 "repository-packages <repo> move-to" - ReInstall all of the
494 packages that are available in the repository, basically the
495 same as: yum reinstall $(repoquery --repoid=<repo> -a).
496 "repository-packages <repo> reinstall" - Tries to do reinstall-
498 old, but if that produces no packages then tries move-to.
499 "repo-pkgs <repo> remove" - Remove all of the packages in the
501 repository, very similar to: yum remove $(repoquery
502 --repoid=<repo> -a). However the repopkgsremove_leaf_only option
503 is obeyed.
504 "repo-pkgs <repo> remove-or-reinstall" - Works like remove for
506 any package that doesn't have the exact same version in another
507 repository. For any package that does have the exact NEVRA in
508 another repository then that version will be reinstalled.
509 "repo-pkgs <repo> remove-or-distro-sync" - Works like remove for
511 any package that doesn't exist in another repository. For any
512 package that does exist it tries to work as if distro-sync was
513 called (with the repo. disabled).
514 version
517 Produces a "version" of the rpmdb, and of the enabled reposito‐
518 ries if "all" is given as the first argument. You can also spec‐
519 ify version groups in the version-groups configuration file. If
520 you pass -v, for verbose mode, more information is listed. The
521 version is calculated by taking an SHA1 hash of the packages (in
522 sorted order), and the checksum_type/checksum_data entries from
523 the yumdb. Note that this rpmdb version is now also used signif‐
524 icantly within yum (esp. in yum history).
525 The version command will now show "groups" of packages as a sep‐
527 arate version, and so takes sub-commands:
528 "version grouplist" - List the defined version groups.
530 "version groupinfo" - Get the complete list of packages within
532 one or more version groups.
533 "version installed" - This is the default, only show the version
535 information for installed packages.
536 "version available" - Only show the version information for
538 available packages.
539 "version all" - Show the version information for installed and
541 available packages.
542 "version nogroups | nogroups-*" - Just show the main version
544 information.
545 "version group-*" - Just show the grouped version information,
547 if more arguments are given then only show the data for those
548 groups.
549 history
552 The history command allows the user to view what has happened in
553 past transactions (assuming the history_record config. option is
554 set). You can use info/list/packages-list/packages-info/summary
555 to view what happened, undo/redo/rollback to act on that infor‐
556 mation and new to start a new history file.
557 The info/list/summary commands take either a transaction id or a
559 package (with wildcards, as in Specifying package names), all
560 three can also be passed no arguments. list can be passed the
561 keyword "all" to list all the transactions.
562 The info command can also take ranges of transaction ids, of the
564 form start..end, which will then display a merged history as if
565 all the transactions in the range had happened at once.
566 Eg. "history info 1..4" will merge the first four transactions
567 and display them as a single transaction.
568 The packages-list/packages-info commands takes a package (with
570 wildcards, as in Specifying package names). And show data from
571 the point of view of that package.
572 The undo/redo/rollback commands take either a single transaction
574 id or the keyword last and an offset from the last transaction
575 (Eg. if you've done 250 transactions, "last" refers to transac‐
576 tion 250, and "last-4" refers to transaction 246). The redo
577 command can also take some optional arguments before you specify
578 the transaction. "force-reinstall" tells it reinstall any pack‐
579 ages that were installed in that transaction (via install,
580 upgrade or downgrade). "force-remove" tells it to forcibly
581 remove any packages that were updated or downgraded.
582 The undo/redo commands act on the specified transaction,
584 undo'ing or repeating the work of that transaction. While the
585 rollback command will undo all transactions up to the point of
586 the specified transaction. For example, if you have 3 transac‐
587 tions, where package A; B and C where installed respectively.
588 Then "undo 1" will try to remove package A, "redo 1" will try to
589 install package A (if it is not still installed), and "rollback
590 1" will try to remove packages B and C. Note that after a "roll‐
591 back 1" you will have a fourth transaction, although the ending
592 rpmdb version (see: yum version) should be the same in transac‐
593 tions 1 and 4.
594 The addon-info command takes a transaction ID, and the packages-
596 list command takes a package (with wildcards).
597 The stats command shows some statistics about the current his‐
599 tory DB.
600 The sync commands allows you to change the rpmdb/yumdb data
602 stored for any installed packages, to whatever is in the current
603 rpmdb/yumdb (this is mostly useful when this data was not stored
604 when the package went into the history DB).
605 In "history list" you can change the behaviour of the 2nd column
607 via the configuration option history_list_view.
608 In "history list" output the Altered column also gives some
610 extra information if there was something not good with the
611 transaction (this is also shown at the end of the package column
612 in the packages-list command).
613 > - The rpmdb was changed, outside yum, after the transaction.
615 < - The rpmdb was changed, outside yum, before the transaction.
616 * - The transaction aborted before completion.
617 # - The transaction completed, but with a non-zero status.
618 E - The transaction completed fine, but had warning/error output
619 during the transaction.
620 P - The transaction completed fine, but problems already existed
621 in the rpmdb.
622 s - The transaction completed fine, but --skip-broken was
623 enabled and had to skip some packages.
624 load-transaction
628 This command will re-load a saved yum transaction file, this
629 allows you to run a transaction on one machine and then use it
630 on another. The two common ways to get a saved yum transaction
631 file are from "yum -q history addon-info last saved_tx" or via
632 the automatic saves in $TMPDIR/yum_save_tx.* when a transaction
633 is solved but not run.
634 Running the command without an argument, or a directory as an
636 argument will try and list the possible files available to load.
637 Showing if the packages are still available, if the rpmdb
638 matches the current rpmdb, how many transaction install/removes
639 members are in the saved transaction and what the filename is.
640 updateinfo
643 This command has a bunch of sub-commands to act on the update‐
644 info in the repositories. The simplest commands are:
645 yum updateinfo info [all | available | installed | updates]
647 yum updateinfo list [all | available | installed | updates]
648 yum updateinfo [summary] [all | available | installed |
649 updates]
650 which all display information about the available update infor‐
652 mation relevant to your machine (including anything installed,
653 if you supply "all").
654 * all Is used to display information about both install and
656 available advisories.
657 * available Is used to display information about just available
658 advisories. This is the default.
659 * installed Is used to display information about just install
660 advisories.
661 * updates This is mostly the same as "available" but it only
662 shows advisory information for packages that can be updated to.
663 They all take as arguments:
666 * <advisory> [advisory...] Is used to display information
668 about one or more advisories.
669 * <package> [package...] Is used to display information about
671 one or more packages.
672 * bugzillas / bzs Is the subset of the updateinfo information,
674 pertaining to the bugzillas.
675 * cves Is the subset of the updateinfo information, pertaining
677 to the CVEs.
678 * enhancement Is the subset of the updateinfo information, per‐
680 taining to enhancements.
681 * bugfix Is the subset of the updateinfo information, pertain‐
683 ing to bugfixes.
684 * security / sec Is the subset of the updateinfo information,
686 pertaining to security.
687 * severity / sev Include security relevant packages of this
689 severity.
690 * recommended Is the subset of the updateinfo information, per‐
692 taining to recommended updates.
693 * new-packages Is the subset of the updateinfo information,
695 pertaining to new packages. These are packages which weren't
696 available at the initial release of your distribution.
697 There are also three sub-commands to remove packages when using
699 "yum shell", they are:
700 yum updateinfo remove-pkgs-ts
702 yum updateinfo exclude-updates
704 yum updateinfo exclude-all
706 they all take the following arguments:
708 * [bzs=foo] [advisories=foo] [cves=foo] [security-severity=foo]
710 [security] [bugfix]
711 and finally there is a command to manually check the running
713 kernel against updateinfo data:
714 yum updateinfo check-running-kernel
716 fssnapshot
719 This command has a few sub-commands to act on the LVM data of
720 the host, to list snapshots and the create and remove them. The
721 simplest commands, to display information about the configured
722 LVM snapshotable devices, are:
723 yum fssnapshot [summary]
725 yum fssnapshot list
726 yum fssnapshot have-space
727 then you can create and delete snapshots using:
729 yum fssnap create
731 yum fssnap delete <device(s)>
732 Configuration Options: fssnap_automatic_pre, fssnap_auto‐
734 matic_post, fssnap_automatic_keep, fssnap_percentage, fss‐
735 nap_devices, fssnap_abort_on_errors
736 fs This command has a few sub-commands to act on the filesystem
739 data of the host, mainly for removing languages/documentation
740 for minimal installs:
741 yum fs filters
743 yum fs filter languages en:es
745 yum fs filter documentation
747 yum fs refilter [package(s)]
749 yum fs refilter-cleanup [package(s)]
751 yum fs du [path]
753 yum fs status [path]
755 yum fs diff [path]
757 the first 3 being a simple interface to change yum.conf altering
760 the tsflags and override_install_langs configurations. The
761 refilter command is an optimized way of calling "yum reinstall"
762 to reinstall the packages with the new filters applied. The
763 refilter-cleanup command is needed because rpm doesn't actually
764 remove the files on reinstall, as it should. And the du/sta‐
765 tus/diff commands are included so you can easily see the space
766 used/saved and any other changes.
767 check Checks the local rpmdb and produces information on any problems
770 it finds. You can pass the check command the arguments "depen‐
771 dencies", "duplicates", "obsoletes" or "provides", to limit the
772 checking that is performed (the default is "all" which does
773 all).
774 help Produces help, either for all commands or if given a command
777 name then the help for that particular command.
778
780 Most command line options can be set using the configuration file as
781 well and the descriptions indicate the necessary configuration option
782 to set.
783 -h, --help
785 Help; display a help message and then quit.
786 -y, --assumeyes
788 Assume yes; assume that the answer to any question which would
789 be asked is yes.
790 Configuration Option: assumeyes
791 --assumeno
793 Assume no; assume that the answer to any question which would be
794 asked is no. This option overrides assumeyes, but is still sub‐
795 ject to alwaysprompt.
796 Configuration Option: assumeno
797 -c, --config=[config file]
799 Specifies the config file location - can take HTTP and FTP URLs
800 and local file paths.
801 -q, --quiet
803 Run without output. Note that you likely also want to use -y.
804 -v, --verbose
806 Run with a lot of debugging output.
807 -d, --debuglevel=[number]
809 Sets the debugging level to [number] - turns up or down the
810 amount of things that are printed. Practical range: 0 - 10
811 Configuration Option: debuglevel
812 -e, --errorlevel=[number]
814 Sets the error level to [number] Practical range 0 - 10. 0 means
815 print only critical errors about which you must be told. 1 means
816 print all errors, even ones that are not overly important. 1+
817 means print more errors (if any) -e 0 is good for cron jobs.
818 Configuration Option: errorlevel
819 --rpmverbosity=[name]
821 Sets the debug level to [name] for rpm scriptlets. 'info' is the
822 default, other options are: 'critical', 'emergency', 'error',
823 'warn' and 'debug'.
824 Configuration Option: rpmverbosity
825 -R, --randomwait=[time in minutes]
827 Sets the maximum amount of time yum will wait before performing
828 a command - it randomizes over the time.
829 -C, --cacheonly
831 Tells yum to run entirely from system cache - does not download
832 or update any headers unless it has to to perform the requested
833 action.
834 --version
836 Reports the yum version number and installed package versions
837 for everything in history_record_packages (can be added to by
838 plugins).
839 --showduplicates
841 Doesn't limit packages to their latest versions in the info,
842 list and search commands (will also affect plugins which use the
843 doPackageLists() API).
844 --installroot=root
846 Specifies an alternative installroot, relative to which all
847 packages will be installed. Think of this like doing "chroot
848 <root> yum" except using --installroot allows yum to work before
849 the chroot is created. Note: You may also want to use the
850 option --releasever=/ when creating the installroot as otherwise
851 the $releasever value is taken from the rpmdb within the
852 installroot (and thus. will be empty, before creation).
853 Configuration Option: installroot
854 --enablerepo=repoidglob
856 Enables specific repositories by id or glob that have been dis‐
857 abled in the configuration file using the enabled=0 option.
858 Configuration Option: enabled
859 --disablerepo=repoidglob
861 Disables specific repositories by id or glob.
862 Configuration Option: enabled
863 --obsoletes
865 This option only has affect for an update, it enables yum´s
866 obsoletes processing logic. For more information see the update
867 command above.
868 Configuration Option: obsoletes
869 -x, --exclude=package
871 Exclude a specific package by name or glob from all reposito‐
872 ries, so yum works as if that package was never in the reposito‐
873 ries. This is commonly used so a package isn't upgraded or
874 installed accidentally, but can be used to remove packages in
875 any way that "yum list" will show packages.
876 Can be disabled using --disableexcludes. Configuration Option:
878 exclude, includepkgs
879 --color=[always|auto|never]
881 Display colorized output automatically, depending on the output
882 terminal, always (using ANSI codes) or never. Note that some
883 commands (Eg. list and info) will do a little extra work when
884 color is enabled. Configuration Option: color
885 --disableexcludes=[all|main|repoid]
887 Disable the excludes defined in your config files. Takes one of
888 three options:
889 all == disable all excludes
890 main == disable excludes defined in [main] in yum.conf
891 repoid == disable excludes defined for that repo
892 --disableincludes=[all|repoid]
894 Disable the includes defined in your config files. Takes one of
895 two options:
896 all == disable all includes
897 repoid == disable includes defined for that repo
898 --disableplugin=plugin
900 Run with one or more plugins disabled, the argument is a comma
901 separated list of wildcards to match against plugin names.
902 --noplugins
904 Run with all plugins disabled.
905 Configuration Option: plugins
906 --nogpgcheck
908 Run with GPG signature checking disabled.
909 Configuration Option: gpgcheck
910 --skip-broken
912 Resolve depsolve problems by removing packages that are causing
913 problems from the transaction.
914 Configuration Option: skip_broken
915 --releasever=version
917 Pretend the current release version is the given string. This is
918 very useful when combined with --installroot. You can also use
919 --releasever=/ to take the releasever information from outside
920 the installroot. Note that with the default upstream cachedir,
921 of /var/cache/yum, using this option will corrupt your cache
922 (and you can use $releasever in your cachedir configuration to
923 stop this).
924 -t, --tolerant
926 This option makes yum go slower, checking for things that
927 shouldn't be possible making it more tolerant of external
928 errors.
929 --downloadonly
931 Don't update, just download. This is done in the background, so
932 the yum lock is released for other operations. This can also be
933 chosen by typing 'd'ownloadonly at the transaction confirmation
934 prompt.
935 --downloaddir=directory
937 Specifies an alternate directory to store packages.
938 --setopt=option=value
940 Set any config option in yum config or repo files. For options
941 in the global config just use: --setopt=option=value for repo
942 options use: --setopt=repoid.option=value
943 --security
945 This option includes packages that say they fix a security
946 issue, in updates.
947 --advisory=ADVS, --advisories=ADVS
949 This option includes in updates packages corresponding to the
950 advisory ID, Eg. FEDORA-2201-123.
951 --bz=BZS
953 This option includes in updates packages that say they fix a
954 Bugzilla ID, Eg. 123.
955 --cve=CVES
957 This option includes in updates packages that say they fix a CVE
958 - Common Vulnerabilities and Exposures ID
959 (http://cve.mitre.org/about/), Eg. CVE-2201-0123.
960 --bugfix
962 This option includes in updates packages that say they fix a
963 bugfix issue.
964 --sec-severity=SEVS, --secseverity=SEVS
966 This option includes in updates security relevant packages of
967 the specified severity.
968
972 The following are the ways which you can invoke yum in list mode. Note
973 that all list commands include information on the version of the pack‐
974 age.
975 OUTPUT
977 The format of the output of yum list is:
980 name.arch [epoch:]version-release repo or @installed-from-repo
982 yum list [all | glob_exp1] [glob_exp2] [...]
985 List all available and installed packages.
986 yum list available [glob_exp1] [...]
988 List all packages in the yum repositories available to be
989 installed.
990 yum list updates [glob_exp1] [...]
992 List all packages with updates available in the yum reposito‐
993 ries.
994 yum list installed [glob_exp1] [...]
996 List the packages specified by args. If an argument does not
997 match the name of an available package, it is assumed to be a
998 shell-style glob and any matches are printed.
999 yum list extras [glob_exp1] [...]
1001 List the packages installed on the system that are not available
1002 in any yum repository listed in the config file.
1003 yum list distro-extras [glob_exp1] [...]
1005 List the packages installed on the system that are not avail‐
1006 able, by name, in any yum repository listed in the config file.
1007 yum list obsoletes [glob_exp1] [...]
1009 List the packages installed on the system that are obsoleted by
1010 packages in any yum repository listed in the config file.
1011 yum list recent
1013 List packages recently added into the repositories. This is
1014 often not helpful, but what you may really want to use is "yum
1015 updateinfo list new" although that relies on updateinfo data
1016 from the repos.
1017
1019 A package can be referred to for install, update, remove, list, info
1020 etc with any of the following as well as globs of any of the following:
1021 name
1023 name.arch
1024 name-ver
1025 name-ver-rel
1026 name-ver-rel.arch
1027 name-epoch:ver-rel.arch
1028 epoch:name-ver-rel.arch
1029 For example: yum remove kernel-2.4.1-10.i686
1031 this will remove this specific kernel-ver-rel.arch.
1032 Or: yum list available 'foo*'
1034 will list all available packages that match 'foo*'. (The
1035 single quotes will keep your shell from expanding the globs.)
1036
1038 The following are the ways which you can invoke yum in clean mode. Note
1039 that "all files" in the commands below means "all files in currently
1040 enabled repositories". If you want to also clean any (temporarily)
1041 disabled repositories you need to use --enablerepo='*' option.
1042 yum clean expire-cache
1045 Eliminate the local data saying when the metadata and mir‐
1046 rorlists were downloaded for each repo. This means yum will
1047 revalidate the cache for each repo. next time it is used. How‐
1048 ever if the cache is still valid, nothing significant was
1049 deleted.
1050 yum clean packages
1053 Eliminate any cached packages from the system. Note that pack‐
1054 ages are not automatically deleted after they are downloaded.
1055 yum clean headers
1058 Eliminate all of the header files, which old versions of yum
1059 used for dependency resolution.
1060 yum clean metadata
1063 Eliminate all of the files which yum uses to determine the
1064 remote availability of packages. Using this option will force
1065 yum to download all the metadata the next time it is run.
1066 yum clean dbcache
1069 Eliminate the sqlite cache used for faster access to metadata.
1070 Using this option will force yum to download the sqlite metadata
1071 the next time it is run, or recreate the sqlite metadata if
1072 using an older repo.
1073 yum clean rpmdb
1076 Eliminate any cached data from the local rpmdb.
1077 yum clean plugins
1080 Tell any enabled plugins to eliminate their cached data.
1081 yum clean all
1084 Does all of the above.
1085
1088 To list all updates that are security relevant, and get a return code
1089 on whether there are security updates use:
1090 yum --security check-update
1092 To upgrade packages that have security errata (upgrades to the latest
1094 available package) use:
1095 yum --security update
1097 To upgrade packages that have security errata (upgrades to the last
1099 security errata package) use:
1100 yum --security update-minimal
1102 To get a list of all BZs that are fixed for packages you have installed
1104 use:
1105 yum updateinfo list bugzillas
1107 To get a list of all security advisories, including the ones you have
1109 already installed use:
1110 yum updateinfo list all security
1112 To get the information on advisory FEDORA-2707-4567 use:
1114 yum updateinfo info FEDORA-2707-4567
1116 To update packages to the latest version which contain fixes for
1118 Bugzillas 123, 456 and 789; and all security updates use:
1119 yum --bz 123 --bz 456 --bz 789 --security update
1121 To update to the packages which just update Bugzillas 123, 456 and 789;
1123 and all security updates use:
1124 yum --bz 123 --bz 456 --bz 789 --security update-minimal
1126 To get an info list of the latest packages which contain fixes for
1128 Bugzilla 123; CVEs CVE-2207-0123 and CVE-2207-3210; and Fedora advi‐
1129 sories FEDORA-2707-4567 and FEDORA-2707-7654 use:
1130 yum --bz 123 --cve CVE-2207-0123 --cve CVE-2207-3210 --advisory
1132 FEDORA-2707-4567 --advisory FEDORA-2707-7654 info updates
1133 To get a list of packages which are "new".
1135 yum updateinfo list new
1137 To get a summary of advisories you haven't installed yet use:
1139 yum updateinfo summary
1141
1145 Yum can be extended through the use of plugins. A plugin is a Python
1146 ".py" file which is installed in one of the directories specified by
1147 the pluginpath option in yum.conf. For a plugin to work, the following
1148 conditions must be met:
1149 1. The plugin module file must be installed in the plugin path as just
1151 described.
1152 2. The global plugins option in /etc/yum.conf must be set to `1'.
1154 3. A configuration file for the plugin must exist in /etc/yum/plugin‐
1156 conf.d/<plugin_name>.conf and the enabled setting in this file must set
1157 to `1'. The minimal content for such a configuration file is:
1158 [main]
1160 enabled = 1
1161 See the yum.conf(5) man page for more information on plugin related
1163 configuration options.
1164
1167 /etc/yum.conf
1168 /etc/yum/version-groups.conf
1169 /etc/yum.repos.d/
1170 /etc/yum/pluginconf.d/
1171 /var/cache/yum/
1172
1175 pkcon [4m(1)
1176 yum.conf [4m(5)
1177 yum-updatesd [4m(8)
1178 package-cleanup [4m(1)
1179 repoquery [4m(1)
1180 yum-complete-transaction [4m(1)
1181 yumdownloader [4m(1)
1182 yum-utils [4m(1)
1183 yum-langpacks [4m(1)
1184 http://yum.baseurl.org/
1185 http://yum.baseurl.org/wiki/Faq
1186 yum search yum
1187
1190 See the Authors file included with this program.
1191
1194 There of course aren't any bugs, but if you find any, you should first
1195 consult the FAQ mentioned above and then email the mailing list:
1196 yum@lists.baseurl.org or filed in bugzilla.
1197Seth Vidal yum(8)