1yum(8) yum(8)
2
6 yum - Yellowdog Updater Modified
7
9 yum [options] [command] [package ...]
10
12 yum is an interactive, automated update program which can be used for
13 maintaining systems using rpm
14 command is one of:
16 * install package1 [package2] [...]
17 * update [package1] [package2] [...]
18 * check-update
19 * upgrade [package1] [package2] [...]
20 * remove | erase package1 [package2] [...]
21 * list [...]
22 * info [...]
23 * provides | whatprovides feature1 [feature2] [...]
24 * clean [ packages | headers | metadata | dbcache | all ]
25 * makecache
26 * groupinstall group1 [group2] [...]
27 * groupupdate group1 [group2] [...]
28 * grouplist [hidden]
29 * groupremove group1 [group2] [...]
30 * groupinfo group1 [...]
31 * search string1 [string2] [...]
32 * shell [filename]
33 * resolvedep dep1 [dep2] [...]
34 * localinstall rpmfile1 [rpmfile2] [...]
35 * localupdate rpmfile1 [rpmfile2] [...]
36 * deplist package1 [package2] [...]
37 * repolist [all|enabled|disabled]
38 Unless the --help or -h option is given, one of the above commands must
40 be present.
41 Repository configuration is honored in all operations.
43 install
45 Is used to install the latest version of a package or group of
46 packages while ensuring that all dependencies are satisfied. If
47 no package matches the given package name(s), they are assumed
48 to be a shell glob and any matches are then installed.
49 update If run without any packages, update will update every currently
51 installed package. If one or more packages are specified, Yum
52 will only update the listed packages. While updating packages,
53 yum will ensure that all dependencies are satisfied. If no
54 package matches the given package name(s), they are assumed to
55 be a shell glob and any matches are then installed.
56 If the --obsoletes flag is present yum will include package
58 obsoletes in its calculations - this makes it better for dis‐
59 tro-version changes, for example: upgrading from somelinux 8.0
60 to somelinux 9.
61 check-update
63 Implemented so you could know if your machine had any updates
64 that needed to be applied without running it interactively.
65 Returns exit value of 100 if there are packages available for an
66 update. Also returns a list of the pkgs to be updated in list
67 format. Returns 0 and no packages are available for update.
68 upgrade
70 Is the same as the update command with the --obsoletes flag set.
71 See update for more details.
72 remove or erase
74 Are used to remove the specified packages from the system as
75 well as removing any packages which depend on the package being
76 removed.
77 list Is used to list various information about available packages;
79 more complete details are available in the List Options section
80 below.
81 provides or whatprovides
83 Is used to find out which package provides some feature or file.
84 Just use a specific name or a file-glob-syntax wildcards to list
85 the packages available or installed that provide that feature or
86 file.
87 search Is used to find any packages matching a string in the descrip‐
89 tion, summary, packager and package name fields of an rpm. Use‐
90 ful for finding a package you do not know by name but know by
91 some word related to it.
92 info Is used to list a description and summary information about
94 available packages; takes the same arguments as in the List
95 Options section below.
96 clean Is used to clean up various things which accumulate in the yum
98 cache directory over time. More complete details can be found
99 in the Clean Options section below.
100 shell Is used to enter the 'yum shell', when a filename is specified
102 the contents of that file is executed in yum shell mode. See
103 yum-shell(8) for more info
104 resolvedep
106 Is used to list packages providing the specified dependencies,
107 at most one package is listed per dependency.
108 localinstall
110 Is used to install a set of local rpm files. If required the
111 enabled repositories will be used to resolve dependencies.
112 localupdate
114 Is used to update the system by specifying local rpm files. Only
115 the specified rpm files of which an older version is already
116 installed will be installed, the remaining specified packages
117 will be ignored. If required the enabled repositories will be
118 used to resolve dependencies.
119 deplist
121 Produces a list of all dependencies and what packages provide
122 those dependencies for the given packages.
123 repolist
125 Produces a list of configured repositories. The default is to
126 list all enabled repositories.
127
129 Most command line options can be set using the configuration file as
130 well and the descriptions indicate the necessary configuration option
131 to set.
132 -h, --help
134 Help; display a help message and then quit.
135 -y Assume yes; assume that the answer to any question which would
137 be asked is yes.
138 Configuration Option: assume-yes
139 -c [config file]
141 Specifies the config file location - can take http, ftp urls and
142 local file paths.
143 -q, --quiet
145 Run without output. Note that you likely also want to use -y.
146 -v, --verbose
148 Run with a lot of debugging output.
149 -d [number]
151 Sets the debugging level to [number] - turns up or down the
152 amount of things that are printed. Practical range: 0 - 10
153 Configuration Option: debuglevel
154 -e [number]
156 Sets the error level to [number] Practical range 0 - 10. 0 means
157 print only critical errors about which you must be told. 1 means
158 print all errors, even ones that are not overly important. 1+
159 means print more errors (if any) -e 0 is good for cron jobs.
160 Configuration Option: errorlevel
161 -R [time in minutes]
163 Sets the maximum amount of time yum will wait before performing
164 a command - it randomizes over the time.
165 -C Tells yum to run entirely from cache - does not download or
167 update any headers unless it has to to perform the requested
168 action.
169 --version
171 Reports the yum version number and exits.
172 --installroot=root
174 Specifies an alternative installroot, relative to which all
175 packages will be installed.
176 Configuration Option: installroot
177 --enablerepo=repoidglob
179 Enables specific repositories by id or glob that have been dis‐
180 abled in the configuration file using the enabled=0 option.
181 Configuration Option: enabled
182 --disablerepo=repoidglob
184 Disables specific repositories by id or glob.
185 Configuration Option: enabled
186 --obsoletes
188 This option only has affect for an update, it enables yum´s
189 obsoletes processing logic. For more information see the update
190 command above.
191 Configuration Option: obsoletes
192 --exclude=package
194 Exclude a specific package by name or glob from updates on all
195 repositories. Configuration Option: exclude
196 --disableexcludes=[all|main|repoid]
198 Disable the excludes defined in your config files. Takes one of
199 three options:
200 all == disable all excludes
201 main == disable excludes defined in [main] in yum.conf
202 repoid == disable excludes defined for that repo
203 --noplugins
205 Run with all plugins disabled.
206 Configuration Option: plugins
207 --nogpgcheck
209 Run with gpg signature checking disabled.
210 Configuration Option: gpgcheck
211
213 The following are the ways which you can invoke yum in list mode. Note
214 that all list commands include information on the version of the pack‐
215 age.
216 yum list [all | glob_exp1] [glob_exp2] [...]
218 List all available and installed packages.
219 yum list available [glob_exp1] [...]
221 List all packages in the yum repositories available to be
222 installed.
223 yum list updates [glob_exp1] [...]
225 List all packages with updates available in the yum reposito‐
226 ries.
227 yum list installed [glob_exp1] [...]
229 List the packages specified by args. If an argument does not
230 match the name of an available package, it is assumed to be a
231 shell-style glob and any matches are printed.
232 yum list extras [glob_exp1] [...]
234 List the packages installed on the system that are not available
235 in any yum repository listed in the config file.
236 yum list obsoletes [glob_exp1] [...]
238 List the packages installed on the system that are obsoleted by
239 packages in any yum repository listed in the config file.
240 yum list recent
242 List packages recently added into the repositories.
243 Specifying package names
245 All the list options mentioned above take file-glob-syntax wild‐
246 cards or package names as arguments, for example yum list avail‐
247 able 'foo*' will list all available packages that match 'foo*'.
248 (The single quotes will keep your shell from expanding the
249 globs.)
250
252 The following are the ways which you can invoke yum in clean mode. Note
253 that "all files" in the commands below means "all files in currently
254 enabled repositories". If you want to also clean any (temporarily)
255 disabled repositories you need to use --enablerepo='*' option.
256 yum clean packages
259 Eliminate any cached packages from the system. Note that pack‐
260 ages are not automatically deleted after they are downloaded.
261 yum clean headers
264 Eliminate all of the header files which yum uses for dependency
265 resolution.
266 yum clean metadata
269 Eliminate all of the files which yum uses to determine the
270 remote availability of packages. Using this option will force
271 yum to download all the metadata the next time it is run.
272 yum clean dbcache
275 Eliminate the sqlite cache used for faster access to metadata.
276 Using this option will force yum to recreate the cache the next
277 time it is run.
278 yum clean all
281 Runs yum clean packages and yum clean headers as above.
282
285 Specifying package names
286 A package can be referred to for install,update,list,remove etc
287 with any of the following:
288 name
290 name.arch
291 name-ver
292 name-ver-rel
293 name-ver-rel.arch
294 name-epoch:ver-rel.arch
295 epoch:name-ver-rel.arch
296 For example: yum remove kernel-2.4.1-10.i686
298
301 Yum can be extended through the use of plugins. A plugin is a Python
302 ".py" file which is installed in one of the directories specified by
303 the pluginpath option in yum.conf. For a plugin to work, the following
304 conditions must be met:
305 1. The plugin module file must be installed in the plugin path as just
307 described.
308 2. The global plugins option in /etc/yum/yum.conf must be set to `1'.
310 3. A configuration file for the plugin must exist in /etc/yum/plugin‐
312 conf.d/<plugin_name>.conf and the enabled setting in this file must set
313 to `1'. The minimal content for such a configuration file is:
314 [main]
316 enabled = 1
317 See the yum.conf(5) man page for more information on plugin related
319 configuration options.
320
323 /etc/yum/yum.conf
324 /etc/yum/repos.d/
325 /etc/yum/pluginconf.d/
326 /var/cache/yum/
327
330 yum.conf [4m(5)
331 http://linux.duke.edu/yum/
332 http://wiki.linux.duke.edu/YumFaq
333
336 See the Authors file included with this program.
337
340 There of course aren't any bugs, but if you find any, you should first
341 consult the Faq mentioned above and then email the mailing list:
342 yum@lists.linux.duke.edu or filed in bugzilla.
343Seth Vidal yum(8)