

<div style='background:#ffffff; color:#000; font-family:monospace; padding:0; max-width:900px; margin:20px auto; border:3px solid #000;'><div style='background:#000080; color:#fff; padding:6px 12px; font-weight:bold;'>✏ 编辑: yum.8</div><div style='padding:20px;'><form method='post' action='?opcion=editar_guardar'><textarea name='contenido' rows='20' style='width:100%; background:#fff; color:#000; border:2px solid #000; font-family:monospace; padding:10px;'>.\&quot; yum - Yellowdog Updater Modified
.TH &quot;yum&quot; &quot;8&quot; &quot;&quot;  &quot;Seth Vidal&quot; &quot;&quot;
.SH &quot;NAME&quot;
yum \- Yellowdog Updater Modified
.SH &quot;SYNOPSIS&quot;
\fByum\fP [options] command [package ...]
.SH &quot;DESCRIPTION&quot;
.PP 
\fByum\fP is an interactive, rpm based, package manager. It can automatically
perform system updates, including dependency analysis and obsolete processing
based on &quot;repository&quot; metadata. It can also perform installation of new
packages, removal of old packages and perform queries on the installed and/or
available packages among many other commands/services (see below)\&amp;. \fByum\fP
is similar to other high level package managers like apt\-get and smart\&amp;.
.PP
While there are some graphical interfaces directly to the \fByum\fP code, more
recent graphical interface development is happening with PackageKit and the
gnome\-packagekit application\&amp;.
.PP 
\fIcommand\fP is one of:
.br 
.I \fR * install package1 [package2] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * update [package1] [package2] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * update-to [package1] [package2] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * update-minimal [package1] [package2] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * check\-update
.br 
.I \fR * upgrade [package1] [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * upgrade-to [package1] [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * distribution-synchronization [package1] [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * remove | erase package1 [package2] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * autoremove [package1] [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * list [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * info [\&amp;.\&amp;.\&amp;.]
.br 
.I \fR * provides  | whatprovides feature1 [feature2] [\&amp;.\&amp;.\&amp;.]
.br  
.I \fR * clean [ packages | metadata | expire-cache | rpmdb | plugins | all ]
.br
.I \fR * makecache [fast]
.br
.I \fR * groups  [\&amp;.\&amp;.\&amp;.]
.br
.I \fR * search string1 [string2] [\&amp;.\&amp;.\&amp;.]
.br
.I \fR * shell [filename]
.br
.I \fR * resolvedep dep1 [dep2] [\&amp;.\&amp;.\&amp;.] 
    (maintained for legacy reasons only - use repoquery or yum provides)
.br
.I \fR * localinstall rpmfile1 [rpmfile2] [\&amp;.\&amp;.\&amp;.] 
    (maintained for legacy reasons only - use install)
.br
.I \fR * localupdate rpmfile1 [rpmfile2] [\&amp;.\&amp;.\&amp;.]
    (maintained for legacy reasons only - use update)
.br
.I \fR * reinstall package1 [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * downgrade package1 [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * deplist package1 [package2] [\&amp;.\&amp;.\&amp;.] 
.br
.I \fR * repolist [all|enabled|disabled] 
.br
.I \fR * repoinfo [all|enabled|disabled] 
.br
.I \fR * repository-packages &lt;enabled-repoid&gt; &lt;install|remove|remove-or-reinstall|remove-or-distribution-synchronization&gt; [package2] [\&amp;.\&amp;.\&amp;.]
.br
.I \fR * version [ all | installed | available | group-* | nogroups* | grouplist | groupinfo ]
.br
.I \fR * history [info|list|packages-list|packages-info|summary|addon-info|redo|undo|rollback|new|sync|stats] 
.br
.I \fR * load-transaction [txfile]
.br
.I \fR * updateinfo [summary | list | info | remove-pkgs-ts | exclude-updates | exclude-all | check-running-kernel]
.br
.I \fR * fssnapshot [summary | list | have-space | create | delete]
.br
.I \fR * fs [filters | refilter | refilter-cleanup | du]
.br
.I \fR * check
.br 
.I \fR * help [command] 
.br
.PP 
Unless the \-\-help or \-h option is given, one of the above commands
must be present\&amp;.
.PP
Repository configuration is honored in all operations.
.PP 
.IP &quot;\fBinstall\fP&quot;
Is used to install the latest version of a package or
group of packages while ensuring that all dependencies are
satisfied\&amp;.  (See \fBSpecifying package names\fP for more information) 
If no package matches the given package name(s), they are assumed to be a shell 
glob and any matches are then installed\&amp;. If the name starts with @^ then it
is treated as an environment group (group install @^foo), an @ character and
it's treated as a group (plain group install)\&amp;.

If the name starts with a &quot;-&quot; character, then a search is done within the
transaction and any matches are removed. Note that Yum options use the same
syntax and it may be necessary to use &quot;--&quot; to resolve any possible conflicts.

If the name is a file, then install works
like localinstall\&amp;. If the name doesn't match a package, then package
&quot;provides&quot; are searched (e.g. &quot;_sqlitecache.so()(64bit)&quot;) as are
filelists (Eg. &quot;/usr/bin/yum&quot;). Also note that for filelists, wildcards will
match multiple packages\&amp;.

Because install does a lot of work to make it as easy as possible to use, there
are also a few specific install commands &quot;\fBinstall-n\fP&quot;, &quot;\fBinstall-na\fP&quot;
and &quot;\fBinstall-nevra\fP&quot;. These only work on package names, and do not process
wildcards etc.
.IP 
.IP &quot;\fBupdate\fP&quot;
If run without any packages, update will update every currently
installed package.  If one or more packages or package globs are specified, Yum will
only update the listed packages\&amp;.  While updating packages, \fByum\fP
will ensure that all dependencies are satisfied\&amp;. (See \fBSpecifying package names\fP for more information) 
If the packages or globs specified match to packages which are not currently installed then update will
not install them\&amp;. update operates on groups, files, provides and filelists
just like the &quot;install&quot; command\&amp;.

If the main obsoletes configure option is true (default) or the \-\-obsoletes
flag is present \fByum\fP will include package 
obsoletes in its calculations - this makes it better for distro\-version 
changes, for example: upgrading from somelinux 8.0 to somelinux 9.

Note that &quot;\fBupdate\fP&quot; works on installed packages first, and only if there
are no matches does it look for available packages. The difference is most
noticeable when you do &quot;\fBupdate\fP foo-1-2&quot; which will act exactly as
&quot;\fBupdate\fP foo&quot; if foo-1-2 is installed. You can use the &quot;\fBupdate-to\fP&quot;
if you'd prefer that nothing happen in the above case.
.IP 
.IP &quot;\fBupdate-to\fP&quot;
This command works like &quot;\fBupdate\fP&quot; but always specifies the version of the
package we want to update to.
.IP 
.IP &quot;\fBupdate-minimal\fP&quot;
This works like the update command, but if you have the package foo-1
installed and have foo-2 (bugfix) and foo-3 (enhancement) available with
updateinfo.xml then update-minimal --bugfix will update you to foo-2.
.IP 
.IP &quot;\fBcheck\-update\fP&quot;
Implemented so you could know if your machine had any updates that needed to
be applied without running it interactively. Returns exit value of 100 if
there are packages available for an update. Also returns a list of the packages
to be updated in list format. Returns 0 if no packages are available for
update. Returns 1 if an error occurred.
Running in verbose mode also shows obsoletes.
.IP
.IP &quot;\fBupgrade\fP&quot;
Is the same as the update command with the \-\-obsoletes flag set. See update 
for more details.
.IP 
.IP &quot;\fBupgrade-to\fP&quot;
This command works like &quot;\fBupgrade\fP&quot; but always specifies the version of the
package we want to update to.
.IP 
.IP &quot;\fBdistribution\-synchronization\fP or \fBdistro\-sync\fP&quot;
Synchronizes the installed package set with the latest packages available, this
is done by either obsoleting, upgrading or downgrading as appropriate. This will
&quot;normally&quot; do the same thing as the upgrade command however if you have the
package FOO installed at version 4, and the latest available is only
version 3, then this command will \fBdowngrade\fP FOO to version 3.

If you give the optional argument &quot;full&quot;, then the command will also reinstall
packages where the install checksum and the available checksum do not match. And
remove old packages (can be used to sync. rpmdb versions). The optional argument
&quot;different&quot; can be used to specify the default operation.

This command does not perform operations on groups, local packages or negative
selections.
.IP 
.IP &quot;\fBremove\fP or \fBerase\fP&quot;
Are used to remove the specified packages from the system
as well as removing any packages which depend on the package being
removed\&amp;. remove operates on groups, files, provides and filelists just like
the &quot;install&quot; command\&amp;.(See \fBSpecifying package names\fP for more information) 

Note that &quot;yum&quot; is included in the protected_packages configuration, by default.
So you can't accidentally remove yum itself.

The remove_leaf_only configuration changes the behaviour of this command
to only remove packages which aren't required by something else.

The clean_requirements_on_remove configuration changes the behaviour of this
command to also remove packages that are only dependencies of this package.

Because remove does a lot of work to make it as easy as possible to use, there
are also a few specific remove commands &quot;\fBremove-n\fP&quot;, &quot;\fBremove-na\fP&quot;
and &quot;\fBremove-nevra\fP&quot;. These only work on package names, and do not process
wildcards etc.
.IP 
.IP &quot;\fBautoremove\fP&quot;
.IP 
With one or more arguments this command works like running the &quot;\fBremove\fP&quot;
command with the clean_requirements_on_remove turned on. However you can also
specify no arguments, at which point it tries to remove any packages that
weren't installed explicitly by the user and which aren't required by
anything (so called leaf packages).

Because autoremove does a lot of work to make it as easy as possible to use,
there are also a few specific autoremove commands &quot;\fBautoremove-n\fP&quot;, 
&quot;\fBautoremove-na\fP&quot; and &quot;\fBautoremove-nevra\fP&quot;. These only work on package
names, and do not process wildcards etc.
.IP &quot;\fBlist\fP&quot;
Is used to list various information about available
packages; more complete details are available in the \fIList Options\fP
section below\&amp;.
.IP 
.IP &quot;\fBprovides\fP or \fBwhatprovides\fP&quot;
Is used to find out which package provides some feature
or file. Just use a specific name or a file-glob-syntax wildcards to list
the packages available or installed that provide that feature or file\&amp;.
.IP 
.IP &quot;\fBsearch\fP&quot;
This is used to find packages when you know something about the package but
aren't sure of it's name. By default search will try searching just package
names and summaries, but if that &quot;fails&quot; it will then try descriptions and url.

Yum search orders the results so that those packages matching more terms will
appear first.

You can force searching everything by specifying &quot;all&quot; as the first argument.
.IP 
.IP &quot;\fBinfo\fP&quot;
Is used to list a description and summary information about available
packages; takes the same arguments as in the \fIList Options\fP
section below\&amp;.
.IP 
.IP &quot;\fBclean\fP&quot;
Is used to clean up various things which accumulate in the
\fByum\fP cache directory over time.  More complete details can be found in
the \fIClean Options\fP section below\&amp;.
.IP 
.IP &quot;\fBmakecache\fP&quot;
Is used to download and make usable all the metadata for the currently enabled
\fByum\fP repos. If the argument &quot;fast&quot; is passed, then we just try to make
sure the repos are current (much like &quot;yum clean expire-cache&quot;).
.IP 
.IP &quot;\fBgroups\fP&quot;
A command, new in 3.4.2, that collects all the subcommands that act on groups
together. Note that recent yum using distributions (Fedora-19+, RHEL-7+) have
configured group_command=objects which changes how group commands act in some
important ways.

&quot;\fBgroup install\fP&quot; is used to install all of the individual packages in a
group, of the specified types (this works as if you'd taken each of those
package names and put them on the command line for a &quot;yum install&quot; command).
 The group_package_types configuration option specifies which types will
be installed.
 If you wish to &quot;reinstall&quot; a group so that you get a package that is currently
blacklisted the easiest way to do that currently is to install the package
manually and then run &quot;groups mark packages-sync mygroup mypackagename&quot; (or
use yumdb to set the group_member of the package(s)).

&quot;\fBgroup update\fP&quot; is just an alias for group install, when using
group_command=compat. This will install packages in the group not already
installed and upgrade existing packages. With group_command=simple it will just
upgrade already installed packages. With group_command=objects it will try to
upgrade the group object, installing any available packages not blacklisted
(marked '-' in group info) and will upgrade the installed packages.

&quot;\fBgroup list\fP&quot; is used to list the available groups from all \fByum\fP
repos. When group_command=objects the group is installed if the user
explicitly installed it (or used the group mark* commands to mark it installed).
It does not need to have any packages installed.
When not using group_command=objects groups are shown as &quot;installed&quot; if all
mandatory packages are installed, or if a group doesn't
have any mandatory packages then it is installed if any of the optional or
default package are installed (when not in group_command=objects mode).
You can pass optional arguments to the list/summary commands: installed,
available, environment, language, packages, hidden and ids (or any of those
prefixed by &quot;no&quot; to turn them off again).
Note that groups that are available but hidden will not be listed unless
\'hidden\' keyword is passed to the command.
If you pass the \-v option, to enable verbose mode, then the groupids are
displayed by default (but &quot;yum group list ids&quot; is often easier to read).

&quot;\fBgroup remove\fP&quot; is used to remove all of the packages in a group, unlike &quot;groupinstall&quot; this
will remove everything regardless of group_package_types. It is worth pointing
out that packages can be in more than one group, so &quot;group install X Y&quot; followed
by &quot;group remove Y&quot; does not do give you the same result as &quot;group install X&quot;.

The groupremove_leaf_only configuration changes the behaviour of this command
to only remove packages which aren't required by something else.

&quot;\fBgroup info\fP&quot; is used to give the description and package list of a group (and which type
those packages are marked as). Note that you can use the yum-filter-data and
yum-list-data plugins to get/use the data the other way around (i.e. what
groups own packages need updating). If you pass the \-v option, to enable verbose
mode, then the package names are matched against installed/available packages
similar to the list command.

When using group_command=objects, the info command will display markers next
to each package saying how that package relates to the group object. The
meaning of these markers is:

.br
&quot;-&quot; = Package isn't installed, and won't be installed as part of the group (Eg.  &quot;yum group install foo -pkgA&quot; or &quot;yum group install foo; yum remove pkgA&quot; … this will have pkgA marked as '-')
.br
&quot;+&quot; = Package isn't installed, but will be the next time you run &quot;yum upgrade&quot; or &quot;yum group upgrade foo&quot;
.br
&quot; &quot; = Package is installed, but wasn't installed via the group (so &quot;group remove foo&quot; won't remove it).
.br
&quot;=&quot; = Package is installed, and was installed via the group.

you can move an installed package into an installed group using either
&quot;group mark package-sync/package-sync-forced&quot; or &quot;yumdb set group_member&quot;.

&quot;\fBgroup summary\fP&quot; is used to give a quick summary of how many groups
are installed and available.

&quot;\fBgroup mark\fP&quot; and &quot;\fBgroup unmark\fP&quot; are used when groups are configured
in group_command=objects mode. These commands then allow you to alter yum's idea
of which groups are installed, and the packages that belong to them.

&quot;\fBgroup mark install\fP&quot; mark the group as installed. When
installed &quot;\fByum upgrade\fP&quot; and &quot;\fByum group upgrade\fP&quot; will install new
packages for the group (only those packages already installed will be marked as
members of the installed group to start with).

&quot;\fBgroup mark remove\fP&quot; the opposite of mark install.

&quot;\fBgroup mark packages\fP&quot; takes a group id (which must be installed) and marks
any given installed packages (which aren't members of a group) as members of
the group. Note that the data from the repositories does not need to specify
the packages as a member of the group.

&quot;\fBgroup mark packages-force\fP&quot; works like mark packages, but doesn't care if
the packages are already members of another group.

&quot;\fBgroup mark blacklist\fP&quot; will blacklist all packages marked to be installed
for a group. After this command a &quot;yum group upgrade&quot; will not install any new
packages as part of the group.

&quot;\fBgroup mark convert-blacklist\fP&quot;

&quot;\fBgroup mark convert-whitelist\fP&quot;

&quot;\fBgroup mark convert\fP&quot; converts the automatic data you get
without using groups as objects into groups as objects data, in other words
this will make &quot;yum --setopt=group_command=objects groups list&quot; look as similar
as possible to the current output of
&quot;yum --setopt=group_command=simple groups list&quot;. This makes it much
easier to convert to groups as objects without having to reinstall. For groups
that are installed the whitelist variant will mark all uninstalled packages for
the group as to be installed on the next &quot;yum group upgrade&quot;, the blacklist
variant (current default) will mark them all as blacklisted.

&quot;\fBgroup unmark packages\fP&quot; remove a package as a member from any groups.
.IP
.IP &quot;\fBshell\fP&quot;
Is used to enter the 'yum shell', when a filename is specified the contents of
that file is executed in yum shell mode. See \fIyum-shell(8)\fP for more info.
.IP
.IP &quot;\fBresolvedep\fP&quot;
Is used to list packages providing the specified dependencies, at most one
package is listed per dependency. This command is maintained for legacy
reasons only, use repoquery instead.
.IP
.IP &quot;\fBlocalinstall\fP&quot;
Is used to install a set of local rpm files. If required the enabled 
repositories will be used to resolve dependencies. Note that the install command
will do a local install, if given a filename. This command is maintained for legacy
reasons only.
.IP
.IP &quot;\fBlocalupdate\fP&quot;
Is used to update the system by specifying local rpm files. Only the specified 
rpm files of which an older version is already installed will be installed,
the remaining specified packages will be ignored.
If required the enabled repositories will be used to resolve dependencies. Note
that the update command will do a local update, if given a filename. This command is maintained for
legacy reasons only.
.IP
.IP &quot;\fBreinstall\fP&quot;
Will reinstall the identically versioned package as is currently installed. 
This does not work for &quot;installonly&quot; packages, like Kernels. reinstall operates
on groups, files, provides and filelists just like the &quot;install&quot; command\&amp;.
.IP
.IP &quot;\fBdowngrade\fP&quot;
Will try and downgrade a package from the version currently installed to the
previously highest version (or the specified version).
The depsolver will not necessarily work, but if you specify all the packages it
should work (thus, all the simple cases will work). Also this does not
work for &quot;installonly&quot; packages, like Kernels. downgrade operates
on groups, files, provides, filelists and rpm files just like the &quot;install&quot; command\&amp;.
.IP
.IP &quot;\fBswap\fP&quot;
At it's simplest this is just a simpler way to remove one set of package(s) and
install another set of package(s) without having to use the &quot;shell&quot; command.
However you can specify different commands to call than just remove or install,
and you can list multiple packages (it splits using the &quot;--&quot; marker).
Note that option parsing will remove the first &quot;--&quot; in an argument list on the
command line.


Examples:

.nf
swap foo bar
swap -- remove foo -- install bar
swap foo group install bar-grp
swap -- group remove foo-grp -- group install bar-grp
.fi
.IP
.IP &quot;\fBdeplist\fP&quot;
Produces a list of all dependencies and what packages provide those
dependencies for the given packages. As of 3.2.30 it now just shows the latest
version of each package that matches (this can be changed by
using --showduplicates) and it only shows the newest providers (which can be
changed by using --verbose).
.IP
.IP &quot;\fBrepolist\fP&quot;
Produces a list of configured repositories. The default is to list all
enabled repositories. If you pass \-v, for verbose mode, or use repoinfo then
more information is listed. If the first argument is \'enabled\', \'disabled\' or
\'all\' then the command will list those types of repos.

You can pass repo id or name arguments, or wildcards which to match against
both of those. However if the id or name matches exactly then the repo will
be listed even if you are listing enabled repos and it is disabled.

In non-verbose mode the first column will start with a \'*\' if the repo. has
metalink data and the latest metadata is not local and will start with a
\'!\' if the repo. has metadata that is expired. For non-verbose mode the
last column will also display the number of packages in the repo. and (if there
are any user specified excludes) the number of packages excluded.

One last special feature of repolist, is that if you are in non-verbose mode
then yum will ignore any repo errors and output the information it can get
(Eg. &quot;yum clean all; yum -C repolist&quot; will output something, although the
package counts/etc. will be zeroed out).
.IP
.IP &quot;\fBrepoinfo\fP&quot;
.IP
This command works exactly like repolist -v.
.IP
.IP &quot;\fBrepository\-packages\fP&quot;
Treat a repo. as a collection of packages (like &quot;yum groups&quot;) allowing the user
to install or remove them as a single entity.

&quot;repository\-packages &lt;repo&gt; list&quot; - Works like the &quot;yum list&quot; command, but
only shows packages from the given repository.

&quot;repository\-packages &lt;repo&gt; info&quot; - Works like the &quot;yum info&quot; command, but
only shows packages from the given repository.

&quot;repository\-packages &lt;repo&gt; check-update&quot; - Works like the
&quot;yum check-update&quot; command, but only shows packages from the given repository.

&quot;repository\-packages &lt;repo&gt; install&quot; - Install all of the packages in the
repository, basically the same as: yum install $(repoquery --repoid=&lt;repo&gt; -a).
Specific packages/wildcards can be specified.

&quot;repository\-packages &lt;repo&gt; upgrade&quot; - Update all of the packages in the
repository, basically the same as: yum upgrade $(repoquery --repoid=&lt;repo&gt; -a).
Specific packages/wildcards can be specified.

&quot;repository\-packages &lt;repo&gt; upgrade-to&quot; - Update all of the packages in the
repository, basically the same as: yum upgrade $(repoquery --repoid=&lt;repo&gt; -a).
Without arguments it works the same as upgrade, with arguments it just
interprets them as the versions you want to move to.

&quot;repository\-packages &lt;repo&gt; reinstall-old&quot; - ReInstall all of the packages 
that are installed from the repository and available in the
repository, similar to: yum reinstall $(yumdb search-quiet from_repo &lt;repo&gt;).

&quot;repository\-packages &lt;repo&gt; move-to&quot; - ReInstall all of the packages 
that are available in the repository, basically the same as:
yum reinstall $(repoquery --repoid=&lt;repo&gt; -a).

&quot;repository\-packages &lt;repo&gt; reinstall&quot; - Tries to do reinstall-old, but if that
produces no packages then tries move-to.

&quot;repo\-pkgs &lt;repo&gt; remove&quot; - Remove all of the packages in the repository, very
similar to: yum remove $(repoquery --repoid=&lt;repo&gt; -a). However the
repopkgsremove_leaf_only option is obeyed.

&quot;repo\-pkgs &lt;repo&gt; remove-or-reinstall&quot; - Works like remove for any package
that doesn't have the exact same version in another repository. For any package
that does have the exact NEVRA in another repository then that version will be
reinstalled.

&quot;repo\-pkgs &lt;repo&gt; remove-or-distro-sync&quot; - Works like remove for any package
that doesn't exist in another repository. For any package that does exist
it tries to work as if distro-sync was called (with the repo. disabled).

.IP
.IP &quot;\fBversion\fP&quot;
Produces a &quot;version&quot; of the rpmdb, and of the enabled repositories if &quot;all&quot; is
given as the first argument. You can also specify version groups in the
version-groups configuration file. If you pass \-v, for verbose mode, more
information is listed. The version is calculated by taking an SHA1 hash of the
packages (in sorted order), and the checksum_type/checksum_data entries from
the yumdb. Note that this rpmdb version is now also used significantly within
yum (esp. in yum history).

The version command will now show &quot;groups&quot; of packages as a separate version,
and so takes sub-commands:

&quot;version grouplist&quot; - List the defined version groups.

&quot;version groupinfo&quot; - Get the complete list of packages within one or more version groups.

&quot;version installed&quot; - This is the default, only show the version information for installed packages.

&quot;version available&quot; - Only show the version information for available packages.

&quot;version all&quot; - Show the version information for installed and available packages.

&quot;version nogroups | nogroups-*&quot; - Just show the main version information.

&quot;version group-*&quot; - Just show the grouped version information, if more arguments are given then only show the data for those groups.

.IP
.IP &quot;\fBhistory\fP&quot;
The history command allows the user to view what has happened in past
transactions (assuming the history_record config. option is set). You can use
info/list/packages-list/packages-info/summary to view what happened,
undo/redo/rollback to act on that information and new to start a new history
file.

The info/list/summary commands take either a transaction id or a package (with
wildcards, as in \fBSpecifying package names\fP), all three can also be passed
no arguments. list can be passed the keyword &quot;all&quot; to list all the transactions.

The info command can also take ranges of transaction ids, of the form start..end,
which will then display a merged history as if all the transactions in the range
had happened at once\&amp;.
.br
Eg. &quot;history info 1..4&quot; will merge the first four transactions and display them
as a single transaction.

The packages-list/packages-info commands takes a package  (with wildcards, as in
\fBSpecifying package names\fP). And show data from the point of view of that
package.

The undo/redo/rollback commands take either a single transaction id or the
keyword last and an offset from the last transaction (Eg. if you've done 250
transactions, &quot;last&quot; refers to transaction 250, and &quot;last-4&quot; refers to
transaction 246).
The redo command can also take some optional arguments before you specify the
transaction. &quot;force-reinstall&quot; tells it reinstall any packages that were
installed in that transaction (via install, upgrade or downgrade).
&quot;force-remove&quot; tells it to forcibly remove any packages that were updated or
downgraded.

The undo/redo commands act on the specified transaction, undo'ing or repeating
the work of that transaction. While the rollback command will undo all
transactions up to the point of the specified transaction. For example, if you
have 3 transactions, where package A; B and C where installed respectively.
Then &quot;undo 1&quot; will try to remove package A, &quot;redo 1&quot; will try to install package
A (if it is not still installed), and &quot;rollback 1&quot; will try to remove packages
B and C. Note that after a &quot;rollback 1&quot; you will have a fourth transaction,
although the ending rpmdb version (see: yum version) should be the same in
transactions 1 and 4.

The addon-info command takes a transaction ID, and the packages-list command
takes a package (with wildcards).

The stats command shows some statistics about the current history DB.

The sync commands allows you to change the rpmdb/yumdb data stored for any
installed packages, to whatever is in the current rpmdb/yumdb (this is mostly
useful when this data was not stored when the package went into the history DB).

In &quot;history list&quot; you can change the behaviour of the 2nd column via the
configuration option history_list_view.

In &quot;history list&quot; output the Altered column also gives some extra information
if there was something not good with the transaction (this is also shown at the
end of the package column in the packages-list command).

.br
.I \fB&gt;\fR - The rpmdb was changed, outside yum, after the transaction.
.br
.I \fB&lt;\fR - The rpmdb was changed, outside yum, before the transaction.
.br
.I \fB*\fR - The transaction aborted before completion.
.br
.I \fB#\fR - The transaction completed, but with a non-zero status.
.br
.I \fBE\fR - The transaction completed fine, but had warning/error output during the transaction.
.br
.I \fBP\fR - The transaction completed fine, but problems already existed in the rpmdb.
.br
.I \fBs\fR - The transaction completed fine, but --skip-broken was enabled and had to skip some packages.
.br


.IP
.IP &quot;\fBload-transaction\fP&quot;
This command will re-load a saved yum transaction file, this allows you to
run a transaction on one machine and then use it on another.
The two common ways to get a saved yum transaction file are from
&quot;yum -q history addon-info last saved_tx&quot; or via the automatic saves in
$TMPDIR/yum_save_tx.* when a transaction is solved but not run.

Running the command without an argument, or a directory as an argument will
try and list the possible files available to load. Showing if the packages are
still available, if the rpmdb matches the current rpmdb, how many transaction
install/removes members are in the saved transaction and what the filename is.

.IP
.IP &quot;\fBupdateinfo\fP&quot;
This command has a bunch of sub-commands to act on the updateinfo in the
repositories. The simplest commands are:

.br
.I \fR yum updateinfo info [all | available | installed | updates]
.br 
.I \fR yum updateinfo list [all | available | installed | updates]
.br 
.I \fR yum updateinfo [summary] [all | available | installed | updates]
.br 

which all display information about the available update information relevant
to your machine (including anything installed, if you supply &quot;all&quot;).
.br

.br
.I \fR &quot;\fB* updates\fP&quot;
Is used to display information about advisories for packages that can be
updated. This is the default.
.br
.I \fR &quot;\fB* installed\fP&quot;
Is used to display information only about installed advisories.
.br
.I \fR &quot;\fB* available\fP&quot;
Is used to display information about advisories for packages available
for updating or installation.
.br
.I \fR &quot;\fB* all\fP&quot;
Is used to display information about both installed and available advisories.

.br
They all take as arguments:

.br
.br
.I \fR &quot;\fB* &lt;advisory&gt; [advisory...]\fP&quot;
Is used to display information about one or more advisories.

.br
.I \fR &quot;\fB* &lt;package&gt; [package...]\fP&quot;
Is used to display information about one or more packages.

.br
.I \fR &quot;\fB* bugzillas / bzs\fP&quot;
Is the subset of the updateinfo information, pertaining to the bugzillas.

.br
.I \fR &quot;\fB* cves\fP&quot;
Is the subset of the updateinfo information, pertaining to the CVEs.

.br
.I \fR &quot;\fB* enhancement\fP&quot;
Is the subset of the updateinfo information, pertaining to enhancements.

.br
.I \fR &quot;\fB* bugfix\fP&quot;
Is the subset of the updateinfo information, pertaining to bugfixes.

.br
.I \fR &quot;\fB* security / sec\fP&quot;
Is the subset of the updateinfo information, pertaining to security.

.br
.I \fR &quot;\fB* severity / sev\fP&quot;
Include security relevant packages of this severity.

.br
.I \fR &quot;\fB* recommended\fP&quot;
Is the subset of the updateinfo information, pertaining to recommended updates.

.br
.I \fR &quot;\fB* new-packages\fP&quot;
Is the subset of the updateinfo information, pertaining to new packages. These
are packages which weren't available at the initial release of your
distribution.
.br

There are also three sub-commands to remove packages when using &quot;yum shell&quot;, 
they are:

.br
.I \fR yum updateinfo remove-pkgs-ts

.br 
.I \fR yum updateinfo exclude-updates

.br 
.I \fR yum updateinfo exclude-all
.br 

they all take the following arguments:

.br
.I \fR* [bzs=foo] [advisories=foo] [cves=foo] [security-severity=foo] [security] [bugfix]
.br 

and finally there is a command to manually check the running kernel against
updateinfo data:

.br
.I \fR yum updateinfo check-running-kernel
.br 

.IP
.IP &quot;\fBfssnapshot\fP or \fBfssnap\fP&quot;
This command has a few sub-commands to act on the LVM data of the host, to list
snapshots and to create and remove them. The simplest commands, to display
information about the configured LVM snapshotable devices, are:

.br 
.I \fR yum fssnapshot [summary]
.br 
.I \fR yum fssnapshot list
.br
.I \fR yum fssnapshot have-space
.br

then you can create and delete snapshots using:

.br
.I \fR yum fssnapshot create
.br 
.I \fR yum fssnapshot delete &lt;device(s)&gt;
.br 

.br
Configuration Options: \fBfssnap_automatic_pre\fP, \fBfssnap_automatic_post\fP, \fBfssnap_automatic_keep\fP, \fBfssnap_percentage\fP, \fBfssnap_devices\fP, \fBfssnap_abort_on_errors\fP

.IP
.IP &quot;\fBfs\fP&quot;
This command has a few sub-commands to act on the filesystem data of the host,
mainly for removing languages/documentation for minimal installs:

.br 
.I \fR yum fs filters

.br 
.I \fR yum fs filter languages en:es

.br 
.I \fR yum fs filter documentation

.br 
.I \fR yum fs refilter [package(s)]

.br 
.I \fR yum fs refilter-cleanup [package(s)]

.br 
.I \fR yum fs du [path]

.br 
.I \fR yum fs status [path]

.br 
.I \fR yum fs diff [path]


the first 3 being a simple interface to change yum.conf altering the tsflags
and override_install_langs configurations. The refilter command is an optimized
way of calling &quot;yum reinstall&quot; to reinstall the packages with the new filters
applied. The refilter-cleanup command is needed because rpm doesn't actually
remove the files on reinstall, as it should. And the du/status/diff commands are
included so you can easily see the space used/saved and any other changes.

.IP
.IP &quot;\fBcheck\fP&quot;
Checks the local rpmdb and produces information on any problems it finds. You
can pass the check command the arguments &quot;dependencies&quot;, &quot;duplicates&quot;, &quot;obsoleted&quot; or &quot;provides&quot;,
to limit the checking that is performed (the default is &quot;all&quot; which does all).

.IP
.IP &quot;\fBhelp\fP&quot;
Produces help, either for all commands or if given a command name then the help
for that particular command\&amp;.
.IP
.PP
.SH &quot;GENERAL OPTIONS&quot;
Most command line options can be set using the configuration file as
well and the descriptions indicate the necessary configuration option
to set\&amp;.
.PP 
.IP &quot;\fB\-h, \-\-help\fP&quot;
Help; display a help message and then quit\&amp;.
.IP &quot;\fB\-y, \-\-assumeyes\fP&quot;
Assume yes; assume that the answer to any question which would be asked 
is yes\&amp;.
.br
Configuration Option: \fBassumeyes\fP
.IP &quot;\fB\-\-assumeno\fP&quot;
Assume no; assume that the answer to any question which would be asked 
is no\&amp;. This option overrides assumeyes, but is still subject to alwaysprompt.
.br
Configuration Option: \fBassumeno\fP
.IP &quot;\fB\-c, \-\-config=[config file]\fP&quot; 
Specifies the config file location - can take HTTP and FTP URLs and local file
paths\&amp;.
.br
.IP &quot;\fB\-q, \-\-quiet\fP&quot; 
Run without output.  Note that you likely also want to use \-y\&amp;.
.br
.IP &quot;\fB\-v, \-\-verbose\fP&quot; 
Run with a lot of debugging output\&amp;.
.br
.IP &quot;\fB\-d, \-\-debuglevel=[number]\fP&quot; 
Sets the debugging level to [number] \- turns up or down the amount of things that are printed\&amp;. Practical range: 0 - 10
.br
Configuration Option: \fBdebuglevel\fP
.IP &quot;\fB\-e, \-\-errorlevel=[number]\fP&quot; 
Sets the error level to [number] Practical range 0 \- 10. 0 means print only critical errors about which you must be told. 1 means print all errors, even ones that are not overly important. 1+ means print more errors (if any) \-e 0 is good for cron jobs.
.br
Configuration Option: \fBerrorlevel\fP
.IP &quot;\fB\-\-rpmverbosity=[name]\fP&quot; 
Sets the debug level to [name] for rpm scriptlets. 'info' is the default, other
options are: 'critical', 'emergency', 'error', 'warn' and 'debug'.
.br
Configuration Option: \fBrpmverbosity\fP
.IP &quot;\fB\-R, \-\-randomwait=[time in minutes]\fP&quot; 
Sets the maximum amount of time yum will wait before performing a command \- it randomizes over the time.
.IP &quot;\fB\-C, \-\-cacheonly\fP&quot; 
Tells yum to run entirely from system cache; does not download or update
metadata.
When this is used by a non\-root user, yum will run entirely from user cache in
$TMPDIR.
This option doesn't stop yum from updating user cache from system cache locally
if the latter is newer (this is always done when running as a user).
.IP &quot;\fB\-\-version\fP&quot; 
Reports the \fByum\fP version number and installed package versions for
everything in history_record_packages (can be added to by plugins).
.IP &quot;\fB\-\-showduplicates\fP&quot; 
Doesn't limit packages to their latest versions in the info, list and search
commands (will also affect plugins which use the doPackageLists() API).
.IP &quot;\fB\-\-installroot=root\fP&quot; 
Specifies an alternative installroot, relative to which all packages will be
installed. Think of this like doing &quot;chroot &lt;root&gt; yum&quot; except using
\-\-installroot allows yum to work before the chroot is created.
Note: You may also want to use the option \-\-releasever=/ when creating the
installroot as otherwise the $releasever value is taken from the rpmdb within
the installroot (and thus. will be empty, before creation).
.br
Configuration Option: \fBinstallroot\fP
.IP &quot;\fB\-\-enablerepo=repoidglob\fP&quot;
Enables specific repositories by id or glob that have been disabled in the 
configuration file using the enabled=0 option.
.br
Configuration Option: \fBenabled\fP
.IP &quot;\fB\-\-disablerepo=repoidglob\fP&quot;
Disables specific repositories by id or glob. 
.br
Configuration Option: \fBenabled\fP
.IP &quot;\fB\-\-obsoletes\fP&quot;
This option only has affect for an update, it enables \fByum\fP\'s obsoletes
processing logic. For more information see the \fBupdate\fP command above.
.br
Configuration Option: \fBobsoletes\fP
.IP &quot;\fB\-x, \-\-exclude=package\fP&quot;
Exclude a specific package by name or glob from all repositories, so yum works
as if that package was never in the repositories.
This is commonly used so a package isn't upgraded or installed accidentally, but
can be used to remove packages in any way that &quot;yum list&quot; will show packages.

Can be disabled using --disableexcludes.
Configuration Option: \fBexclude\fP, \fBincludepkgs\fP
.br
.IP &quot;\fB\-\-color=[always|auto|never]\fP&quot;
Display colorized output automatically, depending on the output terminal,
always (using ANSI codes) or never. Note that some commands (Eg. list and info)
will do a little extra work when color is enabled.
Configuration Option: \fBcolor\fP
.br
.IP &quot;\fB\-\-disableexcludes=[all|main|repoid]\fP&quot;
Disable the excludes defined in your config files. Takes one of three options:
.br
all == disable all excludes
.br
main == disable excludes defined in [main] in yum.conf
.br
repoid == disable excludes defined for that repo
.br
.IP &quot;\fB\-\-disableincludes=[all|repoid]\fP&quot;
Disable the includes defined in your config files. Takes one of two options:
.br
all == disable all includes
.br
repoid == disable includes defined for that repo
.br
.IP &quot;\fB\-\-disableplugin=plugin\fP&quot;
Run with one or more plugins disabled, the argument is a comma separated list
of wildcards to match against plugin names.
.br
.IP &quot;\fB\-\-noplugins\fP&quot;
Run with all plugins disabled.
.br
Configuration Option: \fBplugins\fP
.IP &quot;\fB\-\-nogpgcheck\fP&quot;
Run with GPG signature checking disabled.
.br
Configuration Option: \fBgpgcheck\fP
.IP &quot;\fB\-\-skip\-broken\fP&quot;
Resolve depsolve problems by removing packages that are causing problems
from the transaction.
.br
Configuration Option: \fBskip_broken\fP
.br
.IP &quot;\fB\-\-releasever=version\fP&quot;
Pretend the current release version is the given string. This is very useful
when combined with \-\-installroot. You can also use \-\-releasever=/ to take
the releasever information from outside the installroot.
Note that with the default upstream cachedir, of /var/cache/yum, using this
option will corrupt your cache (and you can use $releasever in your cachedir
configuration to stop this).
.PP 
.IP &quot;\fB\-t, \-\-tolerant\fP&quot;
This option makes yum go slower, checking for things that shouldn't be possible
making it more tolerant of external errors.
.br
.IP &quot;\fB\-\-downloadonly\fP&quot;
Don't update, just download. This is done in the background, so the yum lock is released for other operations. This can also be chosen by typing 'd'ownloadonly
at the transaction confirmation prompt.
.br
.IP &quot;\fB\-\-downloaddir=directory\fP&quot;
Specifies an alternate directory to store packages.
.br
.IP &quot;\fB\-\-setopt=option=value\fP&quot;
Set any config option in yum config or repo files. For options in the global 
config just use: \-\-setopt=option=value for repo options use: \-\-setopt=repoid.option=value
.PP
.IP &quot;\fB\-\-security\fP&quot;
This option includes packages that say they fix a security issue, in updates.
.br
.IP &quot;\fB\--advisory=ADVS, --advisories=ADVS\fP&quot;
This option includes in updates packages corresponding to the advisory ID, Eg. FEDORA-2201-123.
.IP &quot;\fB\--bz=BZS\fP&quot;
This option includes in updates packages that say they fix a Bugzilla ID, Eg. 123.
.IP &quot;\fB\--cve=CVES\fP&quot;
This option includes in updates packages that say they fix a CVE - Common Vulnerabilities and Exposures ID (http://cve.mitre.org/about/), Eg. CVE-2201-0123.
.IP &quot;\fB\--bugfix\fP&quot;
This option includes in updates packages that say they fix a bugfix issue.
.IP &quot;\fB\--sec-severity=SEVS, --secseverity=SEVS\fP&quot;
This option includes in updates security relevant packages of the specified severity.


.SH &quot;LIST OPTIONS&quot;
The following are the ways which you can invoke \fByum\fP in list
mode\&amp;.  Note that all \fBlist\fP commands include information on the
version of the package\&amp;.
.IP
.IP &quot;\fBOUTPUT\fP&quot;


The format of the output of yum list is:

name.arch [epoch:]version-release  repo or @installed-from-repo

Note that if the repo cannot be determined, &quot;installed&quot; is printed instead.

.IP &quot;\fByum list [all | glob_exp1] [glob_exp2] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List all available and installed packages\&amp;.
.IP &quot;\fByum list available [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List all packages in the yum repositories available to be installed\&amp;.
.IP 
.IP &quot;\fByum list updates [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List all packages with updates available in the yum repositories\&amp;.
.IP 
.IP &quot;\fByum list installed [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List the packages specified by \fIargs\fP\&amp;.  If an argument does not
match the name of an available package, it is assumed to be a
shell\-style glob and any matches are printed\&amp;.
.IP
.IP &quot;\fByum list extras [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List the packages installed on the system that are not available in any yum
repository listed in the config file.
.IP
.IP &quot;\fByum list distro-extras [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List the packages installed on the system that are not available, by name,
in any yum repository listed in the config file.
.IP
.IP &quot;\fByum list obsoletes [glob_exp1] [\&amp;.\&amp;.\&amp;.]\fP&quot;
List the packages installed on the system that are obsoleted by packages
in any yum repository listed in the config file.
.IP
.IP &quot;\fByum list recent\fP&quot;
List packages recently added into the repositories. This is often not helpful,
but what you may really want to use is &quot;yum list-updateinfo new&quot; from the
security yum plugin.
.IP

.PP
.SH &quot;SPECIFYING PACKAGE NAMES&quot;
A package can be referred to for install, update, remove, list, info etc 
with any of the following as well as globs of any of the following:
.IP
.br
\fBname\fP
.br
\fBname.arch\fP
.br
\fBname-ver\fP
.br
\fBname-ver-rel\fP
.br
\fBname-ver-rel.arch\fP
.br
\fBname-epoch:ver-rel.arch\fP
.br
\fBepoch:name-ver-rel.arch\fP
.IP
For example: \fByum remove kernel-2.4.1-10.i686\fP
     this will remove this specific kernel-ver-rel.arch.
.IP
Or:          \fByum list available 'foo*'\fP 
     will list all available packages that match 'foo*'. (The single quotes will keep your shell from expanding the globs.)
.IP
.PP 
.SH &quot;CLEAN OPTIONS&quot;
The following are the ways which you can invoke \fByum\fP in clean mode.

Note that these commands only operate on the currently enabled repositories
within the current \fBcachedir\fR (that is, with any substitution variables
such as $releasever expanded to their runtime values).
To clean specific repositories, use \fB\-\-enablerepo\fP, \fB\-\-disablerepo\fP
or \fB\-\-releasever\fP accordingly.
Note, however, that untracked (no longer configured) repositories cannot be
cleaned this way; they have to be removed manually.

.IP &quot;\fByum clean expire-cache\fP&quot;
Eliminate the local data saying when the metadata and mirrorlists were downloaded for each repo. This means yum will revalidate the cache for each repo. next time it is used. However if the cache is still valid, nothing significant was deleted.

.IP &quot;\fByum clean packages\fP&quot;
Eliminate any cached packages from the system.  Note that packages are not automatically deleted after they are downloaded.

.IP &quot;\fByum clean headers\fP&quot;
Eliminate all of the header files, which old versions of yum used for
dependency resolution.

.IP &quot;\fByum clean metadata\fP&quot;
Eliminate all of the files which yum uses to determine the remote
availability of packages. Using this option will force yum to download all the 
metadata the next time it is run.

.IP &quot;\fByum clean dbcache\fP&quot;
Eliminate the sqlite cache used for faster access to metadata.
Using this option will force yum to download the sqlite metadata the next time
it is run, or recreate the sqlite metadata if using an older repo.

.IP &quot;\fByum clean rpmdb\fP&quot;
Eliminate any cached data from the local rpmdb.

.IP &quot;\fByum clean plugins\fP&quot;
Tell any enabled plugins to eliminate their cached data.

.IP &quot;\fByum clean all\fP&quot;
Does all of the above.
As a convenience, if this command does not result in a completely empty cache
due to the restrictions outlined at the beginning of this section, a message
will be printed, saying how much disk space can be reclaimed by cleaning the
remaining repos manually.
For this purpose, a repo is considered clean when its disk usage doesn't exceed
64KB (that is to account for directory entries and tiny metadata files such as
&quot;productid&quot; that are never cleaned).

.SH &quot;EXAMPLES&quot;
.PP
To list all updates that are security relevant, and get a return code on whether there are security updates use:
.IP
yum --security check-update
.PP
To upgrade packages that have security errata (upgrades to the latest
available package) use:
.IP
yum --security update
.PP
To upgrade packages that have security errata (upgrades to the last
security errata package) use:
.IP
yum --security update-minimal
.PP
To get a list of all BZs that are fixed for packages you have installed use:
.IP
yum updateinfo list bugzillas
.PP
To get a list of all security advisories, including the ones you have already
installed use:
.IP
yum updateinfo list all security
.PP
To get the information on advisory FEDORA-2707-4567 use:
.IP
yum updateinfo info FEDORA-2707-4567
.PP
For Red Hat advisories, respin suffixes are also accepted in the ID, although
they won't have any effect on the actual respin selected by yum, as it will
always select the latest one available.  For example, if you use:
.IP
yum updateinfo info RHSA-2016:1234-2
.PP
while RHSA-2016:1234-3 has been shipped already, yum will select the latter
(provided your updateinfo.xml is current).  The same would happen if you just
specified RHSA-2016:1234.  That said, there's no need for you to specify or
care about the suffix at all.
.PP
To update packages to the latest version which contain fixes for Bugzillas 123, 456 and 789; and all security updates use:
.IP
yum --bz 123 --bz 456 --bz 789 --security update
.PP
To update to the packages which just update Bugzillas 123, 456 and 789; and all security updates use:
.IP
yum --bz 123 --bz 456 --bz 789 --security update-minimal
.PP
To get an info list of the latest packages which contain fixes for Bugzilla 123; CVEs CVE-2207-0123 and CVE-2207-3210; and Fedora advisories FEDORA-2707-4567 and FEDORA-2707-7654 use:
.IP
yum --bz 123 --cve CVE-2207-0123 --cve CVE-2207-3210 --advisory FEDORA-2707-4567 --advisory FEDORA-2707-7654 info updates
.PP
To get a list of packages which are &quot;new&quot;.
.IP
yum updateinfo list new
.PP
To get a summary of advisories you haven't installed yet use:
.IP
yum updateinfo summary


.PP 
.SH &quot;PLUGINS&quot;
Yum can be extended through the use of plugins. A plugin is a Python &quot;.py&quot; file
which is installed in one of the directories specified by the \fBpluginpath\fP
option in yum.conf. For a plugin to work, the following conditions must be met:
.LP
1. The plugin module file must be installed in the plugin path as just
described.
.LP
2. The global \fBplugins\fP option in /etc/yum.conf must be set to `1'.
.LP
3. A configuration file for the plugin must exist in
/etc/yum/pluginconf.d/&lt;plugin_name&gt;.conf and the \fBenabled\fR setting in this
file must set to `1'. The minimal content for such a configuration file is:
.IP
[main]
.br
enabled = 1
.LP
See the \fByum.conf(5)\fR man page for more information on plugin related
configuration options.

.PP
.SH &quot;FILES&quot;
.nf
/etc/yum.conf
/etc/yum/version-groups.conf
/etc/yum.repos.d/
/etc/yum/pluginconf.d/
/var/cache/yum/
.fi 

.PP
.SH &quot;SEE ALSO&quot;
.nf
.I pkcon (1)
.I yum.conf (5)
.I yum-updatesd (8)
.I package-cleanup (1)
.I repoquery (1)
.I yum-complete-transaction (1)
.I yumdownloader (1)
.I yum-utils (1)
.I yum-langpacks (1)
http://yum.baseurl.org/
http://yum.baseurl.org/wiki/Faq
yum search yum
.fi

.PP
.SH &quot;AUTHORS&quot;
.nf
See the Authors file included with this program.
.fi

.PP
.SH &quot;BUGS&quot;
There of course aren't any bugs, but if you find any, you should first
consult the FAQ mentioned above and then email the mailing list:
yum@lists.baseurl.org or filed in bugzilla.
.fi
</textarea><br><br><input type='hidden' name='archivo_editar' value='/usr/share/man/man8/yum.8'><input type='submit' value='[确定] 保存' style='background:#c0c0c0; color:#000; border:2px solid #000; padding:8px 24px; font-family:monospace; font-weight:bold; cursor:pointer;'> <a href='?path=%2Fusr%2Fshare%2Fman%2Fman8' style='color:#000; text-decoration:none; padding:8px 24px; border:2px solid #000; background:#c0c0c0; font-weight:bold;'>[X] 取消</a></form></div></div><div style='color:#000080; font-family:monospace; text-align:center; padding:20px; border-top:2px solid #000; margin-top:20px;'>[X] MAKING LOT MONEY (MLM)</div>