Configuration Option: errorlevel -R [time in minutes] Sets the maximum amount of time yum will wait before performing a command - it randomizes over the time. Configuration Option: enabled --obsoletes This option only has affect for an update, it enables yum 's obsoletes processing logic. For more information see the update command above. Note that some commands Eg. Configuration Option: plugins --nogpgcheck Run with gpg signature checking disabled.
Configuration Option: gpgcheck --skip-broken Resolve depsolve problems by removing packages that are causing problems from the transaction. Note that all list commands include information on the version of the package.
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. The single quotes will keep your shell from expanding the globs. Note that "all files" in the commands below means "all files in currently enabled repositories". Tag Description yum clean expire-cache 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. However if the cache is still valid, nothing significant was deleted.
Note that packages are not automatically deleted after they are downloaded. Using this option will force yum to download all the metadata the next time it is run. Using this option will force yum to recreate the cache the next time it is run. MISC Tag Description Specifying package names A package can be referred to for install,update,list,remove etc with any of the following: name name.
A plugin is a Python ". For a plugin to work, the following conditions must be met: 1. The plugin module file must be installed in the plugin path as just described. Is used to install the latest version of a package or group of packages while ensuring that all dependencies are satisfied. Also note that for filelists, wildcards will match multiple packages.. If run without any packages, update will update every currently installed package. Implemented so you could know if your machine had any updates that needed to be applied without running it interactively.
Are used to remove the specified packages from the system as well as removing any packages which depend on the package being removed. Is used to list various information about available packages; more complete details are available in the List Options section below..
Is used to find out which package provides some feature or file. For example, if you have 3 transactions, where package A; B and C where installed respectively. Then " undo 1 " will try to remove pacakge A, " redo 1 " will try to install package A if it is not still installed , and " rollback 1 " will try to remove packages B and C. Note that after a " rollback 1 " 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. In "history list" 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. P - The transaction completed fine, but problems already existed in the rpmdb.
Checks the local rpmdb and produces information on any problems it finds. You can pass the check command the arguments " dependencies " or " duplicates ", to limit the checking that is performed the default is " all " which does both.
The info command can also take ranges of transaction ids, of the form start Produces help, either for all commands or if given a command name then the help for that particular command. Assume yes; assume that the answer to any question which would be asked is yes. Configuration Option: assumeyes. Sets the debugging level to [ number ] and turns up or down the amount of things that are printed. Practical range: 0 - 10 Configuration Option: debuglevel.
Sets the error level to [ number ] Practical range 0 - Configuration Option: errorlevel. Sets the debug level to [ name ] for rpm scriplets. Configuration Option: rpmverbosity. Sets the maximum amount of time yum will wait before performing a command and it randomizes over the time. Tells yum to run entirely from system cache. Does not download or update any headers unless it has to perform the requested action. If you're using this as a user yum will not use the tempcache for the user but will only use the system cache in the system cachedir.
Doesn't limit packages to their latest versions in the info , list and search commands will also affect plugins which use the doPackageLists API. Specifies an alternative installroot , relative to which all packages will be installed. Think of this like doing " chroot root yum ", except using --installroot allows yum to work before the chroot is created.
Configuration Option: installroot. Configuration Option: enabled. This option only has affect for an update, it enables yum 's obsoletes processing logic. For more information see the update command above. Configuration Option: obsoletes. Exclude a specific package by name or glob from updates on all repositories. Configuration Option: exclude. Display colorized output auto matically, depending on the output terminal, always using ANSI codes or never. Note that some commands Eg.
Configuration Option: color. Disable the excludes defined in your config files. Run with one or more plugins disabled, the argument is a comma separated list of wildcards to match against plugin names. Resolve depsolve problems by removing packages that are causing problems from the transaction.
Pretend the current release version is the given string. 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. 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 "productid" that are never cleaned. Valentin Magnan 3 2 2 bronze badges. Paul afk Paul afk 61 1 1 silver badge 3 3 bronze badges. Now you only need to use it. Henk Henk 2 2 silver badges 7 7 bronze badges.
The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science.
Additionally, you can use the yum clean metadata command to clear the metadata cache if any additional XML files caused the corruption. If yum fails with a Fatal error, run database recovery message, you should delete the database and manually rebuild it by using the following commands:. Additionally, deleting and reinstalling the local package might resolve version mismatches.
Unfortunately, there is no easy fix for most dependency issues because of the many factors involved.
0コメント