Note that when specifying more than one transaction, you can also use a range:. You can also view additional information, such as what configuration options were used at the time of the transaction, or from what repository and why were certain packages installed. To determine what additional information is available for a certain transaction, type the following at a shell prompt as root :.
Similarly to yum history info , when no id is provided, yum automatically uses the latest transaction. Another way to refer to the latest transaction is to use the last keyword:. Example output of yum history addon-info. For the fourth transaction in the history, the yum history addon-info command provides the following output:.
In the output of the yum history addon-info command, three types of information are available:. To display a selected type of additional information, run the following command as root :. Apart from reviewing the transaction history, the yum history command provides means to revert or repeat a selected transaction.
To revert a transaction, type the following at a shell prompt as root :. To repeat a particular transaction, as root , run the following command:. Both commands also accept the last keyword to undo or repeat the latest transaction. Note that both yum history undo and yum history redo commands only revert or repeat the steps that were performed during a transaction. If the transaction installed a new package, the yum history undo command will uninstall it, and if the transaction uninstalled a package the command will again install it.
This command also attempts to downgrade all updated packages to their previous version, if these older packages are still available. When managing several identical systems, yum also enables you to perform a transaction on one of them, store the transaction details in a file, and after a period of testing, repeat the same transaction on the remaining systems as well. To store the transaction details to a file, type the following at a shell prompt as root :.
Once you copy this file to the target system, you can repeat the transaction by using the following command as root :. You can configure load-transaction to ignore missing packages or rpmdb version.
For more information on these configuration options see the yum. Yum stores the transaction history in a single SQLite database file. To start new transaction history, run the following command as root :. The old transaction history will be kept, but will not be accessible as long as a newer database file is present in the directory. This file contains one mandatory [main] section, which enables you to set yum options that have global effect, and can also contain one or more [ repository ] sections, which allow you to set repository-specific options.
However, it is recommended to define individual repositories in new or existing. The following are the most commonly used options in the [main] section:. The assumeyes option determines whether or not yum prompts for confirmation of critical actions. Replace value with one of:. Use this option to set the directory where yum stores its cache and database files.
Replace directory with an absolute path to the directory. With this option, you can set yum to consider the exact architecture when updating already installed packages. Replace value with:. With this setting, yum does not install a package for bit architecture to update a package already installed on the system with bit architecture.
Use the gpgcheck option to specify if yum should perform a GPG signature check on packages. With gpgcheck enabled, all packages' signatures are checked. Replace value with on of:. Upgrade only previously installed packages, but do not install packages that have been added to the group in the meantime.
With this option, yum keeps track of the previously installed groups and distinguishes between packages installed as a part of the group and packages installed separately. See Example 9. With this option, you can set yum to record transaction history. This operation takes certain amount of disk space, and some extra time in the transactions, but it provides a lot of information about past operations, which can be displayed with the yum history command.
For more information on the yum history command, see Section 9. Yum uses history records to detect modifications to the rpmdb data base that have been done outside of yum. In such case, yum displays a warning and automatically searches for possible problems caused by altering rpmdb.
Here you can provide a space-separated list of packages which yum can install , but will never update. See the yum. This option sets how many packages listed in the installonlypkgs directive can be installed at the same time. Replace value with an integer representing the maximum number of versions that can be installed simultaneously for any single package listed in installonlypkgs. The keepcache option determines whether yum keeps the cache of headers and packages after successful installation.
Here, value is one of:. Here, value stands for:. The obsoletes option enables the obsoletes process logic during updates. When one package declares in its spec file that it obsoletes another package, the latter package is replaced by the former package when the former package is installed. Obsoletes are declared, for example, when a package is renamed. This is a global switch to enable or disable yum plug-ins, value is one of:. Disabling all plug-ins is not advised because certain plug-ins provide important yum services.
In particular, product-id and subscription-manager plug-ins provide support for the certificate-based Content Delivery Network CDN. Disabling plug-ins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with yum.
For more information about various yum plug-ins, see Section 9. For further information on controlling plug-ins, see Section 9. To avoid conflicts, custom repositories should not use names used by Red Hat repositories.
The following is a bare minimum example of the form a [ repository ] section takes:. Every [ repository ] section must contain the following directives:. If a specific online repository requires basic HTTP authentication, you can specify your user name and password by prepending it to the URL as username : password link.
For more information about yum variables, see Section 9. Other useful [ repository ] directive are:. This is a simple way to tell yum to use or ignore a particular repository, value is one of:. This is an easy way of quickly turning repositories on and off, which is useful when you desire a single package from a repository that you do not want to enable for updates or installs.
Controls parallel downloading of repository packages. Many more [ repository ] options exist, part of them have the same form and function as certain [ main ] options. For example, repository descriptions often include the operating system name. Instead of "Red Hat Enterprise Linux 7", you can now use the following in the. To list the content of a different configuration section or sections, use the command in the following form:.
To list all configuration options and their corresponding values for the main section, type the following at a shell prompt:. Section 9. This section explains how to add, enable, and disable a repository by using the yum-config-manager command.
All files with the. Yum repositories commonly provide their own. To add such a repository to your system and enable it, run the following command as root :. To enable a particular repository or repositories, type the following at a shell prompt as root :. Alternatively, you can use a glob expression to enable all matching repositories:. To enable repositories defined in the [example] , [example-debuginfo] , and [example-source] sections, type:.
When successful, the yum-config-manager --enable command displays the current repository configuration. To disable a yum repository, run the following command as root :. Similarly to yum-config-manager --enable , you can use a glob expression to disable all matching repositories at the same time:. When successful, the yum-config-manager --disable command displays the current configuration. Install the createrepo package:. This creates the necessary metadata for the yum repository and places metadata in a newly created subdirectory repodata.
The repository is now ready to be consumed by yum. See the Section 9. Optional: If you have already used any yum command with newly updated repository, run:. The Optional and Supplementary subscription channels provide additional software packages for Red Hat Enterprise Linux that cover open source licensed software in the Optional channel and proprietary licensed software in the Supplementary channel.
If you decide to install packages from these channels, follow the steps documented in the article called How to access Optional and Supplementary channels, and -devel packages using Red Hat Subscription Manager RHSM? Yum provides plug-ins that extend and enhance its operations. Certain plug-ins are installed by default. Yum always informs you which plug-ins, if any, are loaded and active whenever you call any yum command.
For example:. In particular, the product-id and subscription-manager plug-ins provide support for the certificate-based Content Delivery Network CDN. You can set plug-in specific options in these files. If this option is missing, you can add it manually to the file. If you merely want to disable all yum plug-ins for a single yum command, use the --noplugins option. For example, to disable the aliases plug-in while updating a system, type:.
You can disable multiple plug-ins by separating their names with commas. In addition, you can match multiple plug-in names or shorten long ones by using glob expressions:. It is an updated package manager that allows you to install, remove, update, view, or search software packages. Use the following yum command to display all installed packages:. To check if a specific package is installed with YUM, filter the output with the grep command :.
RPM lists packages by their package name and revision number. Text-wrapping can make this tool harder to read. Use the rpm ——help command for more options, or refer to the documentation. Active 2 years, 4 months ago. Viewed 74k times. Improve this question. Robert Munteanu 4, 6 6 gold badges 26 26 silver badges 47 47 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. Aaron Copley Aaron Copley 3 3 silver badges 9 9 bronze badges.
You need to check main. It is also worth noting that the plugin downloadonly is included in RHEL 6: yum install yum-downloadonly Package yum-plugin-downloadonly Arabicas Filerons Arabicas Filerons 31 2 2 bronze badges. Viewed k times. Improve this question. I don't think this is off-topic because if you are developing software this can be sort of a common thing to install a package but not be able to find exactly where it installed to or where the libraries went.
There is a reopen link under the question, click it to re-open this question, because I think it is very useful. Question closed as off-topic years ago are useful even today. Flags requesting that this question be re-opened are likely to be rejected.
There is a discussion re: this question's topicality here: meta. Show 1 more comment. Active Oldest Votes.
0コメント