yum deplist sqlite
yum [options] [command] [package …]
Configuration Option: assumeyes
Configuration Option: assumeno
Configuration Option: debuglevel
Configuration Option: errorlevel
Configuration Option: rpmverbosity
Configuration Option: installroot
Configuration Option: enabled
Configuration Option: enabled
Configuration Option: obsoletes
all == disable all excludes
main == disable excludes defined in [main] in yum.conf
repoid == disable excludes defined for that repo
all == disable all includes
repoid == disable includes defined for that repo
Configuration Option: plugins
Configuration Option: gpgcheck
Configuration Option: skip_broken
http://cve.mitre.org/about/), Eg. CVE-2201-0123.
command is one of:
* update [package1] [package2] […]
* update-to [package1] [package2] […]
* update-minimal [package1] [package2] […]
* upgrade [package1] [package2] […]
* upgrade-to [package1] [package2] […]
* distribution-synchronization [package1] [package2] […]
* remove | erase package1 [package2] […]
* autoremove [package1] […]
* list […]
* info […]
* provides | whatprovides feature1 [feature2] […]
* clean [ packages | metadata | expire-cache | rpmdb | plugins | all ]
* makecache [fast]
* groups […]
* search string1 [string2] […]
* shell [filename]
* resolvedep dep1 [dep2] […]
* downgrade package1 [package2] […]
* deplist package1 [package2] […]
* repolist [all|enabled|disabled]
* repoinfo [all|enabled|disabled]
* repository-packages <enabled-repoid> <install|remove|remove-or-reinstall|remove-or-distribution-synchronization> [package2] […]
* version [ all | installed | available | group-* | nogroups* | grouplist | groupinfo ]
* history [info|list|packages-list|packages-info|summary|addon-info|redo|undo|rollback|new|sync|stats]
* load-transaction [txfile]
* updateinfo [summary | list | info | remove-pkgs-ts | exclude-updates | exclude-all | check-running-kernel]
* fssnapshot [summary | list | have-space | create | delete]
* fs [filters | refilter | refilter-cleanup | du]
* help [command]
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.
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.
Is the same as the update command with the –obsoletes flag set. See update for more details.
This command works like “upgrade” but always specifies the version of the package we want to update to.
distribution-synchronization / distro-sync
remove / erase
Is used to list various information about available packages; more complete details are available in the List Options section below.
provides / whatprovides
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.
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 “fails” 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 “all” as the first argument.
Is used to list a description and summary information about available packages; takes the same arguments as in the List Options section below.
Is used to clean up various things which accumulate in the yum cache directory over time. More complete details can be found in the 「Clean Options」 section below.
Is used to download and make usable all the metadata for the currently enabled yum repos. If the argument “fast” is passed, then we just try to make sure the repos are current (much like “yum clean expire-cache”).
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.
“group install” 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 “yum install” command).
The group_package_types configuration option specifies which types will be installed.
If you wish to “reinstall” 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 “groups mark packages-sync mygroup mypackagename” (or use yumdb to set the group_member of the package(s)).
“group update” 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.
“group list” is used to list the available groups from all yum 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 “installed” 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 “no” 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 “yum group list ids” is often easier to read).
“group remove” is used to remove all of the packages in a group, unlike “groupinstall” this will remove everything regardless of group_package_types. It is worth pointing out that packages can be in more than one group, so “group install X Y” followed by “group remove Y” does not do give you the same result as “group install X”.
The groupremove_leaf_only configuration changes the behaviour of this command to only remove packages which aren’t required by something else.
“group info” 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:
“+” = Package isn’t installed, but will be the next time you run “yum upgrade” or “yum group upgrade foo”
” ” = Package is installed, but wasn’t installed via the group (so “group remove foo” won’t remove it).
“=” = Package is installed, and was installed via the group.
“group summary” is used to give a quick summary of how many groups are installed and available.
“group mark” and “group unmark” 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.
“group mark install” mark the group as installed. When installed “yum upgrade” and “yum group upgrade” will install new packages for the group (only those packages already installed will be marked as members of the installed group to start with).
“group mark remove” the opposite of mark install.
“group mark packages” 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.
“group mark packages-force” works like mark packages, but doesn’t care if the packages are already members of another group.
“group mark blacklist” will blacklist all packages marked to be installed for a group. After this command a “yum group upgrade” will not install any new packages as part of the group.
“group mark convert-blacklist”
“group mark convert-whitelist”
“group mark convert” converts the automatic data you get without using groups as objects into groups as objects data, in other words this will make “yum –setopt=group_command=objects groups list” look as similar as possible to the current output of “yum –setopt=group_command=simple groups list”. 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 “yum group upgrade”, the blacklist variant (current default) will mark them all as blacklisted.
“group unmark packages” remove a package as a member from any groups.
Is used to enter the ‘yum shell’, when a filename is specified the contents of that file is executed in yum shell mode. See yum-shell(8) for more info.
swap — remove foo — install bar
swap foo group install bar-grp
swap — group remove foo-grp — group install bar-grp
Eg. “history info 1..4” will merge the first four transactions and display them as a single transaction.
< – The rpmdb was changed, outside yum, before the transaction.
* – The transaction aborted before completion.
# – The transaction completed, but with a non-zero status.
E – The transaction completed fine, but had warning/error output during the transaction.
P – The transaction completed fine, but problems already existed in the rpmdb.
s – The transaction completed fine, but –skip-broken was enabled and had to skip some packages.
yum updateinfo list [all | available | installed | updates]
yum updateinfo [summary] [all | available | installed | updates]
- updates Is used to display information about advisories for packages that can be updated. This is the default.
- installed Is used to display information only about installed advisories.
- available Is used to display information about advisories for packages available for updating or installation.
- all Is used to display information about both installed and available advisories.
- <advisory> [advisory…] Is used to display information about one or more advisories.
- <package> [package…] Is used to display information about one or more packages.
- bugzillas / bzs Is the subset of the updateinfo information, pertaining to the bugzillas.
- cves Is the subset of the updateinfo information, pertaining to the CVEs.
- enhancement Is the subset of the updateinfo information, pertaining to enhancements.
- bugfix Is the subset of the updateinfo information, pertaining to bugfixes.
- security / sec Is the subset of the updateinfo information, pertaining to security.
- severity / sev Include security relevant packages of this severity.
- recommended Is the subset of the updateinfo information, pertaining to recommended updates.
- new-packages 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.
yum fssnapshot list
yum fssnapshot have-space
yum fssnapshot delete <device(s)>
SPECIFYING PACKAGE NAMES
- The plugin module file must be installed in the plugin path as just described.
- The global plugins option in /etc/yum.conf must be set to `1′.
- A configuration file for the plugin must exist in /etc/yum/pluginconf.d/<plugin_name>.conf and the enabled setting in this file must set to `1′. The minimal content for such a configuration file is:
enabled = 1
yum search yum