Zen

Source string Source string

189/10000 · 189

The string is read only.

English Actions
The [command]#dnf history# command allows users to review information about a timeline of DNF transactions, the dates and times on when they occurred, the number of packages affected, whether transactions succeeded or were aborted, and if the RPM database was changed between transactions. Additionally, this command can be used to undo or redo certain transactions.
Listing Transactions
To display a list of all transactions, as `root`, either run [command]#dnf history# with no additional arguments, or enter the following command:
[command]#dnf# [option]`history` [option]`list`
To display only transactions in a given range, use the command in the following form:
dnf history list pass:quotes[_start_id_]..pass:quotes[_end_id_]
You can also list only transactions regarding a particular package or packages. To do so, use the command with a package name or a glob expression:
dnf history list pass:quotes[_glob_expression_]…
For example, the list of first five transactions may look as follows:
~]# dnf history list 1..4
Using metadata from Thu Apr 16 13:41:45 2015 (5:47:31 hours old)
ID | Login user | Date a | Action | Altere
4 | root <root> | 2015-04-16 18:35 | Erase | 1
3 | root <root> | 2015-04-16 18:34 | Install | 1
2 | root <root> | 2015-04-16 17:53 | Install | 1
1 | System <unset> | 2015-04-16 14:14 | Install | 668 E
The [command]#dnf history list# command produces tabular output with each row consisting of the following columns:
* `ID` &mdash; an integer value that identifies a particular transaction.
* `Login user` &mdash; the name of the user whose login session was used to initiate a transaction. This information is typically presented in the `pass:attributes[{blank}]_Full Name_ <pass:attributes[{blank}]_username>_pass:attributes[{blank}]` form, however sometimes the command used to perform the transaction is displayed. For transactions that were not issued by a user (such as an automatic system update), `System <unset>` is used instead.
* `Date and time` &mdash; the date and time when a transaction was issued.
* `Action(s)` &mdash; a list of actions that were performed during a transaction as described in xref:DNF.adoc#tabl-DNF-Transaction_History-Actions[Possible values of the Action(s) field].
* `Altered` &mdash; the number of packages that were affected by a transaction, possibly followed by additional information.
[[tabl-DNF-Transaction_History-Actions]]
.Possible values of the Action(s) field
[options="header"]
|Action|Abbreviation|Description
|`Downgrade`|`D`|At least one package has been downgraded to an older version.
|`Erase`|`E`|At least one package has been removed.
|`Install`|`I`|At least one new package has been installed.
|`Obsoleting`|`O`|At least one package has been marked as obsolete.
|`Reinstall`|`R`|At least one package has been reinstalled.
|`Update`|`U`|At least one package has been updated to a newer version.
Reverting and Repeating Transactions
Apart from reviewing the transaction history, the [command]#dnf history# command provides means to revert or repeat a selected transaction. To revert a transaction, type the following at a shell prompt as `root`:
[command]#dnf# [option]`history` [option]`undo` _id_
To repeat a particular transaction, as `root`, run the following command:
[command]#dnf# [option]`history` [option]`redo` _id_
Both commands also accept the `last` keyword to undo or repeat the latest transaction.
Note that both [command]#dnf history undo# and [command]#dnf history redo# commands merely revert or repeat the steps that were performed during a transaction, and will fail if the required packages are not available. For example, if the transaction installed a new package, the [command]#dnf history undo# command will uninstall it and also attempt to downgrade all updated packages to their previous version, but the command will fail if the required packages are not available.
Configuring DNF and DNF Repositories
indexterm:[DNF,configuring DNF and DNF repositories]indexterm:[DNF,DNF repositories,configuring DNF and DNF repositories] The configuration file for DNF and related utilities is located at `/etc/dnf/dnf.conf`. This file contains one mandatory `[main]` section, which allows you to set DNF options that have global effect, and may also contain one or more `[pass:attributes[{blank}]_repository_pass:attributes[{blank}]]` sections, which allow you to set repository-specific options. However, it is recommended to define individual repositories in new or existing `.repo` files in the `/etc/yum.repos.d/` directory. The values you define in individual `[pass:attributes[{blank}]_repository_pass:attributes[{blank}]]` sections of the `/etc/dnf/dnf.conf` file override values set in the `[main]` section.
This section shows you how to:
set global DNF options by editing the `[main]` section of the `/etc/dnf/dnf.conf` configuration file;
set options for individual repositories by editing the `[pass:attributes[{blank}]_repository_pass:attributes[{blank}]]` sections in `/etc/dnf/dnf.conf` and `.repo` files in the `/etc/yum.repos.d/` directory;

Loading…

User avatar None

Source string added

  1. fedora-docs-l10n/fedora-system-administrat
  2. f26/pages/package-management/DNF
  3. English
* `Action(s)` &mdash; a list of actions that were performed during a transaction as described in xref:DNF.adoc#tabl-DNF-Transaction_History-Actions[Possible values of the Action(s) field].
4 years ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/package-management/DNF.adoc:651
String age
4 years ago
Last updated
10 months ago
Source string age
4 years ago
Translation file
pot/f26/pages/package-management/DNF.pot, string 177