[amateur-radio-guide] Update for dnf (except Appendix A)
by John J. McDonough
commit 427c7cf47357baee71453f13cf8eb657f2e6e264
Author: John J. McDonough <jjmcd(a)fedoraproject.org>
Date: Mon May 4 19:52:07 2015 -0400
Update for dnf (except Appendix A)
en-US/antenna-splat.xml | 2 +-
en-US/logging-cqrlog.xml | 2 +-
en-US/logging-qle.xml | 4 ++--
en-US/logging-xlog.xml | 2 +-
en-US/others-cutecw.xml | 2 +-
en-US/others-ibp.xml | 2 +-
en-US/others-xgridloc.xml | 2 +-
7 files changed, 8 insertions(+), 8 deletions(-)
---
diff --git a/en-US/antenna-splat.xml b/en-US/antenna-splat.xml
index c88556b..a17a0b0 100644
--- a/en-US/antenna-splat.xml
+++ b/en-US/antenna-splat.xml
@@ -16,7 +16,7 @@
<para>
Installing <command>splat</command> is straightforward:
<screen>
- su -c 'yum install splat'
+ su -c 'dnf install splat'
</screen>
</para>
<section>
diff --git a/en-US/logging-cqrlog.xml b/en-US/logging-cqrlog.xml
index c13be56..03dca13 100644
--- a/en-US/logging-cqrlog.xml
+++ b/en-US/logging-cqrlog.xml
@@ -10,7 +10,7 @@
<title>Installing CQRLOG</title>
<para>
<package>cqrlog</package> is simply installed like most applications:
- <screen>sudo yum install cqrlog</screen>
+ <screen>sudo dnf install cqrlog</screen>
</para>
</section>
<section>
diff --git a/en-US/logging-qle.xml b/en-US/logging-qle.xml
index f146037..bc6c972 100644
--- a/en-US/logging-qle.xml
+++ b/en-US/logging-qle.xml
@@ -17,10 +17,10 @@
<section>
<title>Installing qle</title>
<para>
- <package>qle</package> can be installed with yum like any
+ <package>qle</package> can be installed with dnf like any
other package:
<screen>
-sudo yum install qle
+sudo dnf install qle
</screen>
However, <package>qle</package> requires some initial setup
before it may be used.
diff --git a/en-US/logging-xlog.xml b/en-US/logging-xlog.xml
index 99c0882..c491616 100644
--- a/en-US/logging-xlog.xml
+++ b/en-US/logging-xlog.xml
@@ -11,7 +11,7 @@
<title>Installing xlog</title>
<para>
<package>xlog</package> is simply installed like most applications:
- <screen>sudo yum install xlog</screen>
+ <screen>sudo dnf install xlog</screen>
</para>
</section>
<section>
diff --git a/en-US/others-cutecw.xml b/en-US/others-cutecw.xml
index 2a54289..aca1727 100644
--- a/en-US/others-cutecw.xml
+++ b/en-US/others-cutecw.xml
@@ -11,7 +11,7 @@
<title>Installing CuteCW</title>
<para>
<package>CuteCW</package> is simply installed like most applications:
- <screen>sudo yum install cutecw</screen>
+ <screen>sudo dnf install cutecw</screen>
</para>
</section>
<section>
diff --git a/en-US/others-ibp.xml b/en-US/others-ibp.xml
index 42ece37..e3078b8 100644
--- a/en-US/others-ibp.xml
+++ b/en-US/others-ibp.xml
@@ -18,7 +18,7 @@
<para>
<package>ibp</package> is simply installed like most applications:
<screen>
-sudo yum install ibp
+sudo dnf install ibp
</screen>
No additional configuration is required, however,
<package>ibp</package> expects that the time on the system is
diff --git a/en-US/others-xgridloc.xml b/en-US/others-xgridloc.xml
index e02fdd4..56098a3 100644
--- a/en-US/others-xgridloc.xml
+++ b/en-US/others-xgridloc.xml
@@ -16,7 +16,7 @@
<package>xgridloc</package> is installed like most applications
in Fedora:
<screen>
- sudo yum install xgridloc
+ sudo dnf install xgridloc
</screen>
</para>
</section>
9 years
[amateur-radio-guide] Update xnec2c full screen image to F22
by John J. McDonough
commit 014b6f7d9266053c5c86d54e0ce9467b7fbecf80
Author: John J. McDonough <jjmcd(a)fedoraproject.org>
Date: Mon May 4 19:13:53 2015 -0400
Update xnec2c full screen image to F22
en-US/images/antenna-xnec2c/Yagi.png | Bin 524214 -> 261121 bytes
1 files changed, 0 insertions(+), 0 deletions(-)
---
diff --git a/en-US/images/antenna-xnec2c/Yagi.png b/en-US/images/antenna-xnec2c/Yagi.png
index f024cf3..91a5db0 100755
Binary files a/en-US/images/antenna-xnec2c/Yagi.png and b/en-US/images/antenna-xnec2c/Yagi.png differ
9 years
[amateur-radio-guide] Update obvious non-F22 images in qle
by John J. McDonough
commit 1775ee1b559775d5a5758876eca0b54826456434
Author: John J. McDonough <jjmcd(a)fedoraproject.org>
Date: Mon May 4 16:02:51 2015 -0400
Update obvious non-F22 images in qle
en-US/images/logging-qle/EditingQSO.png | Bin 333495 -> 257528 bytes
en-US/images/logging-qle/QLEcolors.png | Bin 0 -> 392768 bytes
en-US/images/logging-qle/qle-full.png | Bin 240801 -> 141316 bytes
en-US/logging-qle.xml | 4 ++--
4 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/images/logging-qle/EditingQSO.png b/en-US/images/logging-qle/EditingQSO.png
index 2c0f39f..8bd72a9 100644
Binary files a/en-US/images/logging-qle/EditingQSO.png and b/en-US/images/logging-qle/EditingQSO.png differ
diff --git a/en-US/images/logging-qle/QLEcolors.png b/en-US/images/logging-qle/QLEcolors.png
new file mode 100644
index 0000000..c1a4a58
Binary files /dev/null and b/en-US/images/logging-qle/QLEcolors.png differ
diff --git a/en-US/images/logging-qle/qle-full.png b/en-US/images/logging-qle/qle-full.png
index 6de68d7..9a9d604 100644
Binary files a/en-US/images/logging-qle/qle-full.png and b/en-US/images/logging-qle/qle-full.png differ
diff --git a/en-US/logging-qle.xml b/en-US/logging-qle.xml
index 6b9be9a..f146037 100644
--- a/en-US/logging-qle.xml
+++ b/en-US/logging-qle.xml
@@ -396,9 +396,9 @@ fieldTypes = "---" # mypwr
You can even adjust individual colors to make them as appealing
(or as horrible) as you prefer:
<figure float="0">
- <title>Colors only a mother could love</title>
+ <title>Boring colors</title>
<mediaobject>
- <imageobject><imagedata scale="99" scalefit="1" fileref="images/logging-qle/Awful.png" format="PNG"/></imageobject>
+ <imageobject><imagedata scale="99" scalefit="1" fileref="images/logging-qle/QLEcolors.png" format="PNG"/></imageobject>
<textobject><para>
qle Colors Example
</para>
9 years
[system-administrators-guide] Bump RevHist to 3-1
by stephenw
commit 7f5e4fad77e13aea97e3a2ad01ee513f214026a3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon May 4 15:58:11 2015 +0200
Bump RevHist to 3-1
for DNF chapter
en-US/Revision_History.xml | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 36114c4..0ac9580 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -5,6 +5,22 @@
<title>Revision History</title>
<simpara>
<revhistory>
+
+ <revision>
+ <revnumber>1-3</revnumber>
+ <date>Mon Apr 4 2015</date>
+ <author>
+ <firstname>Stephen</firstname>
+ <surname>Wadeley</surname>
+ <email>swadeley(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Replaced Yum chapter with DNF chapter.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
<revision>
<revnumber>1-2.1</revnumber>
<date>Wed Mar 4 2015</date>
@@ -18,7 +34,8 @@
<member>Added "Working with the GRUB 2 Boot Loader" chapter.</member>
</simplelist>
</revdescription>
- </revision> <revision>
+ </revision>
+ <revision>
<revnumber>1-2</revnumber>
<date>Tue Dec 9 2014</date>
<author>
9 years
[system-administrators-guide] Change entities to refer to Fedora 22
by stephenw
commit 7d26576b3e4fbed2f3b8c457bf2258551c4c81c4
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon May 4 15:52:54 2015 +0200
Change entities to refer to Fedora 22
en-US/System_Administrators_Guide.ent | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/System_Administrators_Guide.ent b/en-US/System_Administrators_Guide.ent
index b34ac8f..a129ed9 100644
--- a/en-US/System_Administrators_Guide.ent
+++ b/en-US/System_Administrators_Guide.ent
@@ -7,8 +7,8 @@
<!-- Additional Entities: -->
<!ENTITY MAJOROS "Fedora">
-<!ENTITY MAJOROSVER "Fedora 21">
+<!ENTITY MAJOROSVER "Fedora 22">
<!ENTITY OSORG "The Fedora Project">
-<!ENTITY PKGOS "fc21">
-<!ENTITY PRODVER "21">
+<!ENTITY PKGOS "fc22">
+<!ENTITY PRODVER "22">
<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=&PRODUCT;&component...;'>http://bugzilla.redhat.com/</ulink>">
9 years
[system-administrators-guide] Rewrote yum chapter to become DNF chapter
by stephenw
commit 76951b8f47841bae12f500531c9960a5d710e568
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon May 4 15:27:41 2015 +0200
Rewrote yum chapter to become DNF chapter
Bug 1206805 - convert yum commands to dnf commands - System
Administrators Guide
en-US/DNF.xml | 1191 +++++++--------------------------------------------------
1 files changed, 135 insertions(+), 1056 deletions(-)
---
diff --git a/en-US/DNF.xml b/en-US/DNF.xml
index 8eb17fb..027524c 100644
--- a/en-US/DNF.xml
+++ b/en-US/DNF.xml
@@ -9,7 +9,7 @@
<important id="important-Secure_Package_Management_with_GPG-Signed_Packages">
<title>Secure package management with GPG-signed packages</title>
<para>
- DNF provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (i.e. package sources), or for individual repositories. When signature verification is enabled, DNF will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <application>RPM</application> packages you download and install on your system are from a trusted source, such as &OSORG;, and were not modified during transfer. See <xref linkend="sec-Configuring_DNF_and_DNF_Repositories" /> for details on enabling signature-checking with DNF, or <xref linkend="s1-check-rpm-sig" /> for information on working with and verifying GPG-signed <application>RPM</application> packages in general.
+ DNF provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (package sources), or for individual repositories. When signature verification is enabled, DNF will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <application>RPM</application> packages you download and install on your system are from a trusted source, such as &OSORG;, and were not modified during transfer. See <xref linkend="sec-Configuring_DNF_and_DNF_Repositories" /> for details on enabling signature-checking with DNF, or <xref linkend="s1-check-rpm-sig" /> for information on working with and verifying GPG-signed <application>RPM</application> packages in general.
</para>
</important>
<para>
@@ -20,7 +20,7 @@
<note id="note-Note_DNF_and_Superuser_Privileges">
<title>DNF and superuser privileges</title>
<para>
- You must have superuser privileges in order to use <command>dnf</command> to install, update or remove packages on your system. All examples in this chapter assume that you have already obtained superuser privileges by using either the <command>su</command> or <command>sudo</command> command.
+ You must have superuser privileges in order to use the <command>dnf</command> command to install, update or remove packages on your system. All examples in this chapter assume that you have already obtained superuser privileges by using either the <command>su</command> or <command>sudo</command> command.
</para>
</note>
<section id="sec-Checking_For_and_Updating_Packages">
@@ -39,51 +39,41 @@
For example:
</para>
<screen>~]# <command>dnf check-update</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
+Using metadata from Mon Apr 20 16:34:10 2015 (2:42:10 hours old)
-PackageKit.x86_64 0.6.14-2.fc15 fedora
-PackageKit-command-not-found.x86_64 0.6.14-2.fc15 fedora
-PackageKit-device-rebind.x86_64 0.6.14-2.fc15 fedora
-PackageKit-glib.x86_64 0.6.14-2.fc15 fedora
-PackageKit-gstreamer-plugin.x86_64 0.6.14-2.fc15 fedora
-PackageKit-gtk-module.x86_64 0.6.14-2.fc15 fedora
-PackageKit-gtk3-module.x86_64 0.6.14-2.fc15 fedora
-PackageKit-yum.x86_64 0.6.14-2.fc15 fedora
-PackageKit-yum-plugin.x86_64 0.6.14-2.fc15 fedora
-gdb.x86_64 7.2.90.20110429-36.fc15 fedora
-kernel.x86_64 2.6.38.6-26.fc15 fedora
-rpm.x86_64 4.9.0-6.fc15 fedora
-rpm-libs.x86_64 4.9.0-6.fc15 fedora
-rpm-python.x86_64 4.9.0-6.fc15 fedora
-yum.noarch 3.2.29-5.fc15 fedora</screen>
- <para>
- The packages in the above output are listed as having updates available. The first package in the list is <application>PackageKit</application>, the graphical package manager. The line in the example output tells us:
+python.x86_64 2.7.9-6.fc22 updates
+python-cryptography.x86_64 0.8.2-1.fc22 updates
+python-libs.x86_64 2.7.9-6.fc22 updates</screen>
+ <para>
+ The packages in the above output are listed as having updates available. The line in the example output tells us:
</para>
<itemizedlist>
<listitem>
<para>
- <computeroutput>PackageKit</computeroutput> — the name of the package
+ <computeroutput>python</computeroutput> — the name of the package,
</para>
</listitem>
<listitem>
<para>
- <computeroutput>x86_64</computeroutput> — the CPU architecture the package was built for
+ <computeroutput>x86_64</computeroutput> — the CPU architecture the package was built for,
</para>
</listitem>
<listitem>
<para>
- <computeroutput>0.6.14</computeroutput> — the version of the updated package to be installed
+ <computeroutput>2.7.9</computeroutput> — the version of the updated package to be installed,
</para>
</listitem>
<listitem>
+ <para>
+ <computeroutput>6.fc22</computeroutput> — the release of the updated package to be installed,
+ </para>
+ </listitem>
+ <listitem>
<para>
- <computeroutput>fedora</computeroutput> — the repository in which the updated package is located
+ <computeroutput>updates-testing</computeroutput> — the repository in which the updated package is located.
</para>
</listitem>
</itemizedlist>
- <para>
- The output also shows us that we can update the kernel (the kernel package), DNF and <application>RPM</application> themselves (the <filename>dnf</filename> and <filename>rpm</filename> packages), as well as their dependencies (such as the <package>kernel-firmware</package>, <package>rpm-libs</package>, and <package>rpm-python</package> packages), all using <command>dnf</command>.
- </para>
</section>
<section id="sec-Updating_Packages">
<title>Updating Packages</title>
@@ -92,7 +82,7 @@ yum.noarch 3.2.29-5.fc15 fedora</scree
<secondary>updating packages</secondary>
</indexterm>
<para>
- You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too.
+ You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package, or packages, you update have updates available themselves, then they are updated too.
</para>
<bridgehead id="bh-Updating_a_Single_Package">
Updating a Single Package
@@ -104,52 +94,43 @@ yum.noarch 3.2.29-5.fc15 fedora</scree
<para>
To update a single package, run the following command as <systemitem class="username">root</systemitem>:
</para>
- <synopsis><command>dnf</command> <option>update</option> <replaceable>package_name</replaceable></synopsis>
+ <synopsis><command>dnf</command> <option>upgrade</option> <replaceable>package_name</replaceable></synopsis>
<para>
- For example, to update the <package>udev</package> package, type:
+ For example, to update the <package>python</package> package, type:
</para>
- <screen>~]# <command>dnf update udev</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-Updating Red Hat repositories.
-INFO:rhsm-app.repolib:repos updated: 0
-Setting up Update Process
-Resolving Dependencies
---> Running transaction check
----> Package gdb.x86_64 0:7.2.90.20110411-34.fc15 will be updated
----> Package gdb.x86_64 0:7.2.90.20110429-36.fc15 will be an update
---> Finished Dependency Resolution
-
-Dependencies Resolved
-
-================================================================================
- Package Arch Version Repository Size
-================================================================================
-Updating:
- gdb x86_64 7.2.90.20110429-36.fc15 fedora 1.9 M
+ <screen>~]# <command>dnf upgrade python</command>
+Using metadata from Mon Apr 20 16:38:16 2015 (2:42:14 hours old)
+Dependencies resolved.
+==================================================================
+ Package Arch Version Repository Size
+==================================================================
+Upgrading:
+ python x86_64 2.7.9-6.fc22 updates 92 k
+ python-libs x86_64 2.7.9-6.fc22 updates 5.8 M
Transaction Summary
-================================================================================
-Upgrade 1 Package(s)
+==================================================================
+Upgrade 2 Packages
-Total download size: 1.9 M
+Total download size: 5.9 M
Is this ok [y/N]:</screen>
<para>
- This output contains several items of interest:
+ This output contains:
</para>
<orderedlist>
<listitem>
<para>
- <computeroutput>Loaded plugins:</computeroutput> — <command>dnf</command> always informs you which <application>DNF</application> plug-ins are installed and enabled. Here, <command>dnf</command> is using the <application>langpacks</application>, <application>presto</application>, and <application>refresh-packagekit</application> plug-ins. See <xref linkend="sec-DNF_Plugins" /> for general information on <application>DNF</application> plug-ins, or to <xref linkend="sec-Plugin_Descriptions" /> for descriptions of specific plug-ins.
+ <computeroutput>python.x86_64</computeroutput> — you can download and install new <package>python</package> package.
</para>
</listitem>
<listitem>
- <para>
- <computeroutput>gdb.x86_64</computeroutput> — you can download and install new <package>gdb</package> package.
- </para>
- </listitem>
+ <para>
+ <computeroutput>python-libs.x86_64</computeroutput> — DNF has resolved that the <package>python-libs</package> package is a required dependency of the <package>python</package> package.
+ </para>
+ </listitem>
<listitem>
<para>
- <command>dnf</command> presents the update information and then prompts you as to whether you want it to perform the update; <command>dnf</command> runs interactively by default. If you already know which transactions <command>dnf</command> plans to perform, you can use the <option>-y</option> option to automatically answer <command>yes</command> to any questions <command>dnf</command> may ask (in which case it runs non-interactively). However, you should always examine which changes <command>dnf</command> plans to make to the system so that you can easily troubleshoot any problems that might arise.
+ DNF presents the update information and then prompts you as to whether you want it to perform the update; DNF runs interactively by default. If you already know which transactions DNF plans to perform, you can use the <option>-y</option> option to automatically answer <command>yes</command> to any questions DNF may ask (in which case it runs non-interactively). However, you should always examine which changes DNF plans to make to the system so that you can easily troubleshoot any problems that might arise.
</para>
<para>
If a transaction does go awry, you can view DNF's transaction history by using the <command>dnf history</command> command as described in <xref linkend="sec-DNF-Transaction_History" />.
@@ -159,10 +140,10 @@ Is this ok [y/N]:</screen>
<important id="important-Important-Updating_and_Installing_Kernels_with_DNF">
<title>Updating and installing kernels with DNF</title>
<para>
- <command>dnf</command> always <emphasis>installs</emphasis> a new kernel in the same sense that <application>RPM</application> installs a new kernel when you use the command <command>rpm -i kernel</command>. Therefore, you do not need to worry about the distinction between <emphasis>installing</emphasis> and <emphasis>upgrading</emphasis> a kernel package when you use <command>dnf</command>: it will do the right thing, regardless of whether you are using the <command>dnf update</command> or <command>dnf install</command> command.
+ DNF always <emphasis>installs</emphasis> a new kernel in the same sense that <application>RPM</application> installs a new kernel when you use the command <command>rpm -i kernel</command>. Therefore, you do not need to worry about the distinction between <emphasis>installing</emphasis> and <emphasis>upgrading</emphasis> a kernel package when you use the <command>dnf</command> command: it will do the right thing, regardless of whether you are using the <command>dnf upgrade</command> or <command>dnf install</command> command.
</para>
<para>
- When using <application>RPM</application>, on the other hand, it is important to use the <command>rpm -i kernel</command> command (which installs a new kernel) instead of <command>rpm -u kernel</command> (which <emphasis>replaces</emphasis> the current kernel). See <xref linkend="sec-Installing_and_Upgrading" /> for more information on installing/updating kernels with <application>RPM</application>.
+ When using <application>RPM</application>, on the other hand, it is important to use the <command>rpm -i kernel</command> command (which installs a new kernel) instead of <command>rpm -u kernel</command> (which <emphasis>replaces</emphasis> the current kernel). See <xref linkend="sec-Installing_and_Upgrading" /> for more information on installing and updating kernels with <application>RPM</application>.
</para>
</important>
<bridgehead id="bh-Updating_All_Packages_and_Their_Dependencies">
@@ -173,10 +154,10 @@ Is this ok [y/N]:</screen>
<secondary>updating all packages and dependencies</secondary>
</indexterm>
<para>
- To update all packages and their dependencies, simply enter <command>dnf update</command> (without any arguments):
+ To update all packages and their dependencies, enter <command>dnf upgrade</command> without any arguments:
</para>
- <screen><command>dnf update</command></screen>
- <bridgehead id="bh-Updating_Security-Related_Packages">
+ <screen><command>dnf upgrade</command></screen>
+ <!--<bridgehead id="bh-Updating_Security-Related_Packages"> I CANNOT FIND THIS PLUG_IN. I think updateinfo will provide this function
Updating Security-Related Packages
</bridgehead>
<indexterm>
@@ -195,7 +176,7 @@ Is this ok [y/N]:</screen>
</indexterm>
<para>
Discovering which packages have security updates available and then updating those packages quickly and easily is important. DNF provides the plug-in for this purpose. The <application>security</application> plug-in extends the <command>dnf</command> command with a set of highly-useful security-centric commands, subcommands and options. See <xref linkend="sec-Plugin_Descriptions" /> for specific information.
- </para>
+ </para>-->
</section>
<section id="sec-Preserving_Configuration_File_Changes">
<title>Preserving Configuration File Changes</title>
@@ -291,12 +272,12 @@ komparator.x86_64 : Kompare and merge two folders
<tertiary>Glob expressions</tertiary>
</indexterm>
<para>
- Be careful to escape the glob expressions when passing them as arguments to a <command>dnf</command> command, otherwise the Bash shell will interpret these expressions as <firstterm>pathname expansions</firstterm>, and potentially pass all files in the current directory that match the globs to <command>dnf</command>. To make sure the glob expressions are passed to <command>dnf</command> as intended, either:
+ Be careful to escape the glob expressions when passing them as arguments to a <command>dnf</command> command, otherwise the Bash shell will interpret these expressions as <firstterm>pathname expansions</firstterm>, and potentially pass all files in the current directory that match the globs to DNF. To make sure the glob expressions are passed to DNF as intended, either:
</para>
<itemizedlist>
<listitem>
<para>
- escape the wildcard characters by preceding them with a backslash character
+ escape the wildcard characters by preceding them with a backslash character; or,
</para>
</listitem>
<listitem>
@@ -623,17 +604,14 @@ yum-3.2.29-4.fc15.noarch
<note id="note-Finding_which_package_owns_a_file">
<title>Finding which package owns a file</title>
<para>
- If you know you want to install the package that contains the <filename>named</filename> binary, but you do not know in which <filename class="directory">bin</filename> or <filename class="directory">sbin</filename> directory is the file installed, use the <command>dnf provides</command> command with a glob expression:
+ If you know you want to install the package that contains the <filename>named</filename> binary, but you do not know in which <filename class="directory">/usr/bin</filename> or <filename class="directory">/usr/sbin</filename> directory is the file installed, use the <command>dnf provides</command> command with a glob expression:
</para>
<screen>~]# <command>dnf provides "*bin/named"</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-32:bind-9.8.0-3.P1.fc15.i686 : The Berkeley Internet Name Domain (BIND) DNS
- : (Domain Name System) server
-Repo : fedora
-Matched from:
-Filename : /usr/sbin/named</screen>
+Using metadata from Thu Apr 16 13:41:45 2015 (4:23:50 hours old)
+bind-32:9.10.2-1.fc22.x86_64 : The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
+Repo : @System</screen>
<para>
- <command>dnf provides "*/<replaceable>file_name</replaceable>"</command> is a common and useful trick to find the packages that contain <replaceable>file_name</replaceable>.
+ <command>dnf provides "*/<replaceable>file_name</replaceable>"</command> will find all the packages that contain <replaceable>file_name</replaceable>.
</para>
</note>
<bridgehead id="bh-Installing_a_Package_Group">
@@ -648,42 +626,41 @@ Filename : /usr/sbin/named</screen>
<secondary>installing a package group with DNF</secondary>
</indexterm>
<para>
- A package group is similar to a package: it is not useful by itself, but installing one pulls a group of dependent packages that serve a common purpose. A package group has a name and a <firstterm>groupid</firstterm>. The <command>dnf grouplist -v</command> command lists the names of all package groups, and, next to each of them, their groupid in parentheses. The groupid is always the term in the last pair of parentheses, such as <literal>kde-desktop</literal> in the following example:
+ A package group is similar to a package: it is not useful by itself, but installing one pulls a group of dependent packages that serve a common purpose. A package group has a name and a <firstterm>groupid</firstterm> (<acronym>GID</acronym>). The <command>dnf grouplist -v</command> command lists the names of all package groups, and, next to each of them, their groupid in parentheses. The groupid is always the term in the last pair of parentheses, such as <literal>kde-desktop-environment</literal> in the following example:
</para>
<screen>~]# <command>dnf -v grouplist kde\*</command>
-Not loading "blacklist" plugin, as it is disabled
-Loading "langpacks" plugin
-Loading "presto" plugin
-Loading "refresh-packagekit" plugin
-Not loading "whiteout" plugin, as it is disabled
-Adding en_US to language list
-Config time: 0.900
-DNF Version: 3.2.29
-Setting up Group Process
-rpmdb time: 0.002
-group time: 0.995
-Available Groups:
- KDE Software Compilation (kde-desktop)
- KDE Software Development (kde-software-development)
-Done</screen>
+cachedir: /var/cache/dnf/x86_64/22
+Loaded plugins: builddep, config-manager, copr, playground, debuginfo-install, download, generate_completion_cache, kickstart, needs-restarting, noroot, protected_packages, Query, reposync, langpacks
+initialized Langpacks plugin
+DNF version: 0.6.5
+repo: using cache for: fedora
+not found deltainfo for: Fedora 22 - x86_64
+not found updateinfo for: Fedora 22 - x86_64
+repo: using cache for: updates-testing
+repo: using cache for: updates
+not found updateinfo for: Fedora 22 - x86_64 - Updates
+Using metadata from Thu Apr 16 13:41:45 2015 (4:37:51 hours old)
+Available environment groups:
+ KDE Plasma Workspaces (kde-desktop-environment)</screen>
<para>
You can install a package group by passing its full group name (without the groupid part) to <command>groupinstall</command>:
- </para>
<synopsis><command>dnf</command> <option>groupinstall</option> <replaceable>group_name</replaceable></synopsis>
+ Multi-word names must be quoted.
+ </para>
<para>
You can also install by groupid:
</para>
<synopsis><command>dnf</command> <option>groupinstall</option> <replaceable>groupid</replaceable></synopsis>
<para>
- You can even pass the groupid (or quoted name) to the <command>install</command> command if you prepend it with an <keysym>@</keysym>-symbol (which tells <command>dnf</command> that you want to perform a <command>groupinstall</command>):
+ You can even pass the groupid, or quoted name, to the <command>install</command> command if you prepend it with an <keysym>@</keysym>-symbol (which tells <command>dnf</command> that you want to perform a <command>groupinstall</command>):
</para>
<synopsis><command>dnf</command> <option>install</option> @<replaceable>group</replaceable></synopsis>
<para>
- For example, the following are alternative but equivalent ways of installing the <literal>KDE Desktop</literal> group:
+ For example, the following are alternative but equivalent ways of installing the <literal>KDE Plasma Workspaces</literal> group:
</para>
- <screen>~]# <command>dnf groupinstall "KDE Desktop"</command>
-~]# <command>dnf groupinstall kde-desktop</command>
-~]# <command>dnf install @kde-desktop</command></screen>
+ <screen>~]# <command>dnf groupinstall "KDE Plasma Workspaces"</command>
+~]# <command>dnf groupinstall kde-desktop-environment</command>
+~]# <command>dnf install @kde-desktop-environment</command></screen>
</section>
<section id="sec-Removing">
<title>Removing Packages</title>
@@ -747,7 +724,7 @@ Done</screen>
<warning id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It">
<title>Removing a package when other packages depend on it</title>
<para>
- DNF is not able to remove a package without also removing packages which depend on it. This type of operation can only be performed by <application>RPM</application>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash. For further information, refer to <xref linkend="s2-rpm-uninstalling" /> in the <application>RPM</application> chapter.
+ DNF is not able to remove a package without also removing packages which depend on it. This type of operation can only be performed by <application>RPM</application>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and terminate unexpectedly. For further information, refer to <xref linkend="s2-rpm-uninstalling" /> in the <application>RPM</application> chapter.
</para>
</warning>
<bridgehead id="bh-Removing_a_Package_Group">
@@ -759,11 +736,11 @@ Done</screen>
<synopsis><command>dnf</command> <option>groupremove</option> <replaceable>group</replaceable></synopsis>
<synopsis><command>dnf</command> <option>remove</option> @<replaceable>group</replaceable></synopsis>
<para>
- The following are alternative but equivalent ways of removing the <literal>KDE Desktop</literal> group:
+ The following are alternative but equivalent ways of removing the <literal>KDE Plasma Workspaces</literal> group:
</para>
- <screen>~]# <command>dnf groupremove "KDE Desktop"</command>
-~]# <command>dnf groupremove kde-desktop</command>
-~]# <command>dnf remove @kde-desktop</command></screen>
+ <screen>~]# <command>dnf groupremove "KDE Plasma Workspaces"</command>
+~]# <command>dnf groupremove kde-desktop-environment</command>
+~]# <command>dnf remove @kde-desktop-environment</command></screen>
<important id="important-Package_Group_Removal">
<title>Intelligent package group removal</title>
<indexterm>
@@ -775,7 +752,7 @@ Done</screen>
<secondary>uninstalling package groups with DNF</secondary>
</indexterm>
<para>
- When you tell <application>dnf</application> to remove a package group, it will remove every package in that group, even if those packages are members of other package groups or dependencies of other installed packages. However, you can instruct <command>dnf</command> to remove only those packages which are not required by any other packages or groups by adding the <option>groupremove_leaf_only=1</option> directive to the <literal>[main]</literal> section of the <filename>/etc/dnf.conf</filename> configuration file. For more information on this directive, refer to <xref linkend="sec-Setting_main_Options" />.
+ When you use the <command>dnf</command> command to remove a package group, it will remove every package in that group, except packages installed separately by a user or packages which are a dependency of a package installed previously.
</para>
</important>
</section>
@@ -788,7 +765,7 @@ Done</screen>
Listing Transactions
</bridgehead>
<para>
- To display a list of twenty most recent transactions, as <systemitem class="username">root</systemitem>, either run <command>dnf history</command> with no additional arguments, or type the following at a shell prompt:
+ To display a list of the twenty most recent transactions, as <systemitem class="username">root</systemitem>, either run <command>dnf history</command> with no additional arguments, or enter the following command:
</para>
<synopsis><command>dnf</command> <option>history</option> <option>list</option></synopsis>
<para>
@@ -806,16 +783,14 @@ Done</screen>
<para>
For example, the list of first five transactions may look as follows:
</para>
- <screen>~]# <command>dnf history list 1..5</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-ID | Login user | Date and time | Action(s) | Altered
+ <screen>~]# <command>dnf history list 1..4</command>
+Using metadata from Thu Apr 16 13:41:45 2015 (5:47:31 hours old)
+ID | Login user | Date a | Action | Altere
-------------------------------------------------------------------------------
- 5 | Jaromir ... <jhradilek> | 2011-07-29 15:33 | Install | 1
- 4 | Jaromir ... <jhradilek> | 2011-07-21 15:10 | Install | 1
- 3 | Jaromir ... <jhradilek> | 2011-07-16 15:27 | I, U | 73
- 2 | System <unset> | 2011-07-16 15:19 | Update | 1
- 1 | System <unset> | 2011-07-16 14:38 | Install | 1106
-history list</screen>
+ 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</screen>
<para>
All forms of the <command>dnf history list</command> command produce tabular output with each row consisting of the following columns:
</para>
@@ -956,7 +931,7 @@ history list</screen>
<literal><</literal>
</entry>
<entry>
- Before the transaction finished, the <filename>rpmdb</filename> database was changed outside DNF.
+ Before the transaction finished, the <database>rpmdb</database> database was changed outside DNF.
</entry>
</row>
<row>
@@ -964,7 +939,7 @@ history list</screen>
<literal>></literal>
</entry>
<entry>
- After the transaction finished, the <filename>rpmdb</filename> database was changed outside DNF.
+ After the transaction finished, the <database>rpmdb</database> database was changed outside DNF.
</entry>
</row>
<row>
@@ -980,7 +955,7 @@ history list</screen>
<literal>#</literal>
</entry>
<entry>
- The transaction finished successfully, but <command>dnf</command> returned a non-zero exit code.
+ The transaction finished successfully, but DNF returned a non-zero exit code.
</entry>
</row>
<row>
@@ -996,78 +971,26 @@ history list</screen>
<literal>P</literal>
</entry>
<entry>
- The transaction finished successfully, but problems already existed in the <filename>rpmdb</filename> database.
+ The transaction finished successfully, but problems already existed in the <database>rpmdb</database> database.
</entry>
</row>
- <row>
+ <!-- <row>
<entry>
<literal>s</literal>
</entry>
<entry>
- The transaction finished successfully, but the <option>--skip-broken</option> command line option was used and certain packages were skipped.
+ The transaction finished successfully, but <remark>There is no <option>skip-broken</option> in DNF, but is there still "s"?</remark> certain packages were skipped.
</entry>
- </row>
+ </row>-->
</tbody>
</tgroup>
</table>
- <para>
- DNF also allows you to display a summary of all past transactions. To do so, run the command in the following form as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>summary</option></synopsis>
- <para>
- To display only transactions in a given range, type:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>summary</option> <replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
- <para>
- Similarly to the <command>dnf history list</command> command, you can also display a summary of transactions regarding a certain package or packages by supplying a package name or a glob expression:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>summary</option> <replaceable>glob_expression</replaceable>…</synopsis>
- <para>
- For instance, a summary of the transaction history displayed above would look like the following:
- </para>
- <screen>~]# <command>dnf history summary 1..5</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-Login user | Time | Action(s) | Altered
--------------------------------------------------------------------------------
-Jaromir ... <jhradilek> | Last day | Install | 1
-Jaromir ... <jhradilek> | Last week | Install | 1
-Jaromir ... <jhradilek> | Last 2 weeks | I, U | 73
-System <unset> | Last 2 weeks | I, U | 1107
-history summary</screen>
- <para>
- All forms of the <command>dnf history summary</command> command produce simplified tabular output similar to the output of <command>dnf history list</command>.
- </para>
- <para>
- As shown above, both <command>dnf history list</command> and <command>dnf history summary</command> are oriented towards transactions, and although they allow you to display only transactions related to a given package or packages, they lack important details, such as package versions. To list transactions from the perspective of a package, run the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>package-list</option> <replaceable>glob_expression</replaceable>…</synopsis>
- <para>
- For example, to trace the history of <package>subscription-manager</package> and related packages, type the following at a shell prompt:
- </para>
- <screen>~]# <command>dnf history package-list subscription-manager\*</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-ID | Action(s) | Package
--------------------------------------------------------------------------------
- 3 | Updated | subscription-manager-0.95.11-1.el6.x86_64
- 3 | Update | 0.95.17-1.el6_1.x86_64
- 3 | Updated | subscription-manager-firstboot-0.95.11-1.el6.x86_64
- 3 | Update | 0.95.17-1.el6_1.x86_64
- 3 | Updated | subscription-manager-gnome-0.95.11-1.el6.x86_64
- 3 | Update | 0.95.17-1.el6_1.x86_64
- 1 | Install | subscription-manager-0.95.11-1.el6.x86_64
- 1 | Install | subscription-manager-firstboot-0.95.11-1.el6.x86_64
- 1 | Install | subscription-manager-gnome-0.95.11-1.el6.x86_64
-history package-list</screen>
- <para>
- In this example, three packages were installed during the initial system installation: <package>subscription-manager</package>, <package>subscription-manager-firstboot</package>, and <package>subscription-manager-gnome</package>. In the third transaction, all these packages were updated from version 0.95.11 to version 0.95.17.
- </para>
+
+
<bridgehead id="bh-DNF-Transaction_History-Examining">
Examining Transactions
</bridgehead>
- <para>
- To display the summary of a single transaction, as <systemitem class="username">root</systemitem>, use the <command>dnf history summary</command> command in the following form:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>summary</option> <replaceable>id</replaceable></synopsis>
+
<para>
To examine a particular transaction or transactions in more detail, run the following command as <systemitem class="username">root</systemitem>:
</para>
@@ -1079,70 +1002,25 @@ history package-list</screen>
<para>
The following is sample output for two transactions, each installing one new package:
</para>
- <screen>~]# <command>dnf history info 4..5</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-Transaction ID : 4..5
-Begin time : Thu Jul 21 15:10:46 2011
-Begin rpmdb : 1107:0c67c32219c199f92ed8da7572b4c6df64eacd3a
-End time : 15:33:15 2011 (22 minutes)
-End rpmdb : 1109:1171025bd9b6b5f8db30d063598f590f1c1f3242
-User : Jaromir Hradilek <jhradilek>
+ <screen>~]# <command>dnf history info 2..3</command>
+Using metadata from Thu Apr 16 13:41:45 2015 (6:03:11 hours old)
+Transaction ID : 2..3
+Begin time : Thu Apr 16 17:53:16 2015
+Begin rpmdb : 668:2020a6af3a20aa4d9416684ed355e95937f2d05b
+End time : 18:34:57 2015 (41 minutes)
+End rpmdb : 670:6bcc1521043cfb2e6b97398a14f6f4b854e3a0cc
+User : root <root>
Return-Code : Success
-Command Line : install screen
-Command Line : install yum-plugin-fs-snapshot
+Command Line : install bind
+Command Line : install zd1211-firmware
Transaction performed with:
- Installed rpm-4.8.0-16.el6.x86_64
- Installed yum-3.2.29-17.el6.noarch
- Installed yum-metadata-parser-1.1.2-16.el6.x86_64
+ Installed dnf-0.6.5-1.fc22.noarch @fedora
+ Installed rpm-4.12.0.1-9.fc22.x86_64 @updates-testing
Packages Altered:
- Install screen-4.0.3-16.el6.x86_64
- Install yum-plugin-fs-snapshot-1.1.30-6.el6.noarch
-history info</screen>
- <para>
- 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 <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>addon-info</option> <replaceable>id</replaceable></synopsis>
- <para>
- Similarly to <command>dnf history info</command>, when no <replaceable>id</replaceable> is provided, <command>dnf</command> automatically uses the latest transaction. Another way to refer to the latest transaction is to use the <literal>last</literal> keyword:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>addon-info</option> <option>last</option></synopsis>
- <para>
- For instance, for the first transaction in the previous example, the <command>dnf history addon-info</command> command would provide the following output:
- </para>
- <screen>~]# <command>dnf history addon-info 4</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-Transaction ID: 4
-Available additional history information:
- config-main
- config-repos
- saved_tx
+ Install bind-32:9.10.2-1.fc22.x86_64 @fedora
+ Install zd1211-firmware-1.4-10.fc21.noarch @fedora</screen>
-history addon-info</screen>
- <para>
- In this example, three types of information are available:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <computeroutput>config-main</computeroutput> — global DNF options that were in use during the transaction. See <xref linkend="sec-Setting_main_Options" /> for information on how to change global options.
- </para>
- </listitem>
- <listitem>
- <para>
- <computeroutput>config-repos</computeroutput> — options for individual DNF repositories. See <xref linkend="sec-Setting_repository_Options" /> for information on how to change options for individual repositories.
- </para>
- </listitem>
- <listitem>
- <para>
- <computeroutput>saved_tx</computeroutput> — the data that can be used by the <command>dnf load-transaction</command> command in order to repeat the transaction on another machine (see below).
- </para>
- </listitem>
- </itemizedlist>
- <para>
- To display selected type of additional information, run the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>addon-info</option> <replaceable>id</replaceable> <replaceable>information</replaceable></synopsis>
- <bridgehead id="bh-DNF-Transaction_History-Reverting">
+ <bridgehead id="bh-DNF-Transaction_History-Reverting">
Reverting and Repeating Transactions
</bridgehead>
<para>
@@ -1157,29 +1035,9 @@ history addon-info</screen>
Both commands also accept the <literal>last</literal> keyword to undo or repeat the latest transaction.
</para>
<para>
- Note that both <command>dnf history undo</command> and <command>dnf history redo</command> commands merely revert or repeat the steps that were performed during a transaction: if the transaction installed a new package, the <command>dnf history undo</command> command will uninstall it, and vice versa. If possible, this command will also attempt to downgrade all updated packages to their previous version, but these older packages may no longer be available. If you need to be able to restore the system to the state before an update, consider using the <application>fs-snapshot</application> plug-in described in <xref linkend="sec-Plugin_Descriptions" />.
- </para>
- <para>
- When managing several identical systems, DNF also allows 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 <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>-q</option> <option>history</option> <option>addon-info</option> <replaceable>id</replaceable> <option>saved_tx</option> > <filename>file_name</filename></synopsis>
- <para>
- Once you copy this file to the target system, you can repeat the transaction by using the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>load-transaction</option> <replaceable>file_name</replaceable></synopsis>
- <para>
- Note, however that the <literal>rpmdb</literal> version stored in the file must by identical to the version on the target system. You can verify the <literal>rpmdb</literal> version by using the <command>dnf version nogroups</command> command.
- </para>
- <bridgehead id="bh-DNF-Transaction_History-New">
- Starting New Transaction History
- </bridgehead>
- <para>
- DNF stores the transaction history in a single SQLite database file. To start new transaction history, run the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf</command> <option>history</option> <option>new</option></synopsis>
- <para>
- This will create a new, empty database file in the <filename class="directory">/var/lib/dnf/history/</filename> directory. The old transaction history will be kept, but will not be accessible as long as a newer database file is present in the directory.
+ Note that both <command>dnf history undo</command> and <command>dnf history redo</command> commands merely revert or repeat the steps that were performed during a transaction: if the transaction installed a new package, the <command>dnf history undo</command> command will uninstall it, and vice versa. If possible, this command will also attempt to downgrade all updated packages to their previous version, but these older packages may no longer be available. <!--If you need to be able to restore the system to the state before an update, consider using the <application>snapper</application> plug-in described in <xref linkend="sec-Plugin_Descriptions" />.-->
</para>
+
</section>
</section>
<section id="sec-Configuring_DNF_and_DNF_Repositories">
@@ -1194,7 +1052,7 @@ history addon-info</screen>
<tertiary>configuring DNF and DNF repositories</tertiary>
</indexterm>
<para>
- The configuration file for <command>dnf</command> and related utilities is located at <filename>/etc/dnf.conf</filename>. This file contains one mandatory <literal>[main]</literal> section, which allows you to set DNF options that have global effect, and may also contain one or more <literal>[<replaceable>repository</replaceable>]</literal> sections, which allow you to set repository-specific options. However, best practice is to define individual repositories in new or existing <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/dnf.repos.d/</filename>directory. The values you define in the <literal>[main]</literal> section of the <filename>/etc/dnf.conf</filename> file may override values set in individual <literal>[<replaceable>repository</replaceable>]</literal> sections.
+ The configuration file for DNF and related utilities is located at <filename>/etc/dnf/dnf.conf</filename>. This file contains one mandatory <literal>[main]</literal> section, which allows you to set DNF options that have global effect, and may also contain one or more <literal>[<replaceable>repository</replaceable>]</literal> sections, which allow you to set repository-specific options. However, it is recommended to define individual repositories in new or existing <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename>directory. The values you define in the <literal>[main]</literal> section of the <filename>/etc/dnf/dnf.conf</filename> file may override values set in individual <literal>[<replaceable>repository</replaceable>]</literal> sections.
</para>
<para>
This section shows you how to:
@@ -1202,17 +1060,17 @@ history addon-info</screen>
<itemizedlist>
<listitem>
<para>
- set global DNF options by editing the <literal>[main]</literal> section of the <filename>/etc/dnf.conf</filename> configuration file;
+ set global DNF options by editing the <literal>[main]</literal> section of the <filename>/etc/dnf/dnf.conf</filename> configuration file;
</para>
</listitem>
<listitem>
<para>
- set options for individual repositories by editing the <literal>[<replaceable>repository</replaceable>]</literal> sections in <filename>/etc/dnf.conf</filename> and <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/dnf.repos.d/</filename> directory;
+ set options for individual repositories by editing the <literal>[<replaceable>repository</replaceable>]</literal> sections in <filename>/etc/dnf/dnf.conf</filename> and <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename> directory;
</para>
</listitem>
<listitem>
<para>
- use DNF variables in <filename>/etc/dnf.conf</filename> and files in the <filename>/etc/dnf.repos.d/</filename> directory so that dynamic version and architecture values are handled correctly;
+ use DNF variables in <filename>/etc/dnf/dnf.conf</filename> and files in the <filename>/etc/yum.repos.d/</filename> directory so that dynamic version and architecture values are handled correctly;
</para>
</listitem>
<listitem>
@@ -1233,76 +1091,26 @@ history addon-info</screen>
<secondary>setting [main] options</secondary>
</indexterm>
<para>
- The <filename>/etc/dnf.conf</filename> configuration file contains exactly one <literal>[main]</literal> section, and while some of the key-value pairs in this section affect how <command>dnf</command> operates, others affect how DNF treats repositories.
+ The <filename>/etc/dnf/dnf.conf</filename> configuration file contains exactly one <literal>[main]</literal> section, and while some of the key-value pairs in this section affect how <command>dnf</command> operates, others affect how DNF treats repositories.
-You can add many additional options under the <literal>[main]</literal> section heading in <filename>/etc/dnf.conf</filename>.
+You can add many additional options under the <literal>[main]</literal> section heading in <filename>/etc/dnf/dnf.conf</filename>.
</para>
<para>
- A sample <filename>/etc/dnf.conf</filename> configuration file can look like this:
+ A sample <filename>/etc/dnf/dnf.conf</filename> configuration file can look like this:
</para>
<programlisting>[main]
-cachedir=/var/cache/dnf/$basearch/$releasever
-keepcache=0
-debuglevel=2
-logfile=/var/log/dnf.log
-exactarch=1
-obsoletes=1
gpgcheck=1
-plugins=1
installonly_limit=3
-
-<lineannotation>[comments abridged]</lineannotation>
-
-# PUT YOUR REPOS HERE OR IN separate files named file.repo
-# in /etc/dnf.repos.d</programlisting>
+clean_requirements_on_remove=true</programlisting>
<para>
The following are the most commonly-used options in the <literal>[main]</literal> section:
</para>
<variablelist>
<varlistentry>
- <term><option>assumeyes</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>0</literal> — <command>dnf</command> should prompt for confirmation of critical actions it performs. This is the default.
- </para>
- <para>
- <literal>1</literal> — Do not prompt for confirmation of critical <command>dnf</command> actions. If <option>assumeyes=1</option> is set, <command>dnf</command> behaves in the same way that the command line option <option>-y</option> does.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>cachedir</option>=<replaceable>directory</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>directory</replaceable> is an absolute path to the directory where DNF should store its cache and database files. By default, DNF's cache directory is <filename class="directory">/var/cache/dnf/$basearch/$releasever</filename>.
- </para>
- <para>
- See <xref linkend="sec-Using_DNF_Variables" /> for descriptions of the <varname>$basearch</varname> and <varname>$releasever</varname> DNF variables.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
<term><option>debuglevel</option>=<replaceable>value</replaceable></term>
<listitem>
<para>
- …where <replaceable>value</replaceable> is an integer between <literal>1</literal> and <literal>10</literal>. Setting a higher <option>debuglevel</option> value causes <command>dnf</command> to display more detailed debugging output. <option>debuglevel=0</option> disables debugging output, while <option>debuglevel=2</option> is the default.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>exactarch</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>0</literal> — Do not take into account the exact architecture when updating packages.
- </para>
- <para>
- <literal>1</literal> — Consider the exact architecture when updating packages. With this setting, <command>dnf</command> will not install an i686 package to update an i386 package already installed on the system. This is the default.
+ …where <replaceable>value</replaceable> is an integer between <literal>0</literal> and <literal>10</literal>. Setting a higher <option>debuglevel</option> value causes <command>dnf</command> to display more detailed debugging output. <option>debuglevel=0</option> disables debugging output, and <option>debuglevel=2</option> is the default.
</para>
</listitem>
</varlistentry>
@@ -1327,7 +1135,7 @@ installonly_limit=3
<literal>1</literal> — Enable GPG signature-checking on all packages in all repositories, including local package installation. <option>gpgcheck=1</option> is the default, and thus all packages' signatures are checked.
</para>
<para>
- If this option is set in the <literal>[main]</literal> section of the <filename>/etc/dnf.conf</filename> file, it sets the GPG-checking rule for all repositories. However, you can also set <option>gpgcheck=<replaceable>value</replaceable></option> for individual repositories instead; that is, you can enable GPG-checking on one repository while disabling it on another. Setting <option>gpgcheck=<replaceable>value</replaceable></option> for an individual repository in its corresponding <filename class="extension">.repo</filename> file overrides the default if it is present in <filename>/etc/dnf.conf</filename>.
+ If this option is set in the <literal>[main]</literal> section of the <filename>/etc/dnf/dnf.conf</filename> file, it sets the GPG-checking rule for all repositories. However, you can also set <option>gpgcheck=<replaceable>value</replaceable></option> for individual repositories instead; you can enable GPG-checking on one repository while disabling it on another. Setting <option>gpgcheck=<replaceable>value</replaceable></option> for an individual repository in its corresponding <filename class="extension">.repo</filename> file overrides the default if it is present in <filename>/etc/dnf/dnf.conf</filename>.
</para>
<para>
For more information on GPG signature-checking, refer to <xref linkend="s1-check-rpm-sig" />.
@@ -1335,30 +1143,13 @@ installonly_limit=3
</listitem>
</varlistentry>
<varlistentry>
- <term><option>groupremove_leaf_only</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>0</literal> — <command>dnf</command> should <emphasis>not</emphasis> check the dependencies of each package when removing a package group. With this setting, <command>dnf</command> removes all packages in a package group, regardless of whether those packages are required by other packages or groups. <option>groupremove_leaf_only=0</option> is the default.
- </para>
- <para>
- <literal>1</literal> — <command>dnf</command> should check the dependencies of each package when removing a package group, and remove only those packages which are not not required by any other package or group.
- </para>
- <para>
- For more information on removing packages, refer to <xref linkend="important-Package_Group_Removal" />.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
<term><option>installonlypkgs</option>=<replaceable>space</replaceable> <replaceable>separated</replaceable> <replaceable>list</replaceable> <replaceable>of</replaceable> <replaceable>packages</replaceable></term>
<listitem>
<para>
Here you can provide a space-separated list of packages which <command>dnf</command> can <emphasis>install</emphasis>, but will never <emphasis>update</emphasis>. See the <emphasis role="bold">dnf.conf</emphasis>(5) manual page for the list of packages which are install-only by default.
</para>
<para>
- If you add the <option>installonlypkgs</option> directive to <filename>/etc/dnf.conf</filename>, you should ensure that you list <emphasis>all</emphasis> of the packages that should be install-only, including any of those listed under the <literal>installonlypkgs</literal> section of <emphasis role="bold">dnf.conf</emphasis>(5). In particular, kernel packages should always be listed in <option>installonlypkgs</option> (as they are by default), and <option>installonly_limit</option> should always be set to a value greater than <literal>2</literal> so that a backup kernel is always available in case the default one fails to boot.
+ If you add the <option>installonlypkgs</option> directive to <filename>/etc/dnf/dnf.conf</filename>, you should ensure that you list <emphasis>all</emphasis> of the packages that should be install-only, including any of those listed under the <literal>installonlypkgs</literal> section of <emphasis role="bold">dnf.conf</emphasis>(5). In particular, kernel packages should always be listed in <option>installonlypkgs</option> (as they are by default), and <option>installonly_limit</option> should always be set to a value greater than <literal>2</literal> so that a backup kernel is always available in case the default one fails to boot.
</para>
</listitem>
</varlistentry>
@@ -1369,7 +1160,7 @@ installonly_limit=3
…where <replaceable>value</replaceable> is an integer representing the maximum number of versions that can be installed simultaneously for any single package listed in the <option>installonlypkgs</option> directive.
</para>
<para>
- The defaults for the <option>installonlypkgs</option> directive include several different kernel packages, so be aware that changing the value of <option>installonly_limit</option> will also affect the maximum number of installed versions of any single kernel package. The default value listed in <filename>/etc/dnf.conf</filename> is <option>installonly_limit=3</option>, and it is not recommended to decrease this value, particularly below <literal>2</literal>.
+ The defaults for the <option>installonlypkgs</option> directive include several different kernel packages, so be aware that changing the value of <option>installonly_limit</option> will also affect the maximum number of installed versions of any single kernel package. The default value listed in <filename>/etc/dnf/dnf.conf</filename> is <option>installonly_limit=3</option>, and it is not recommended to decrease this value, particularly below <literal>2</literal>.
</para>
</listitem>
</varlistentry>
@@ -1387,84 +1178,9 @@ installonly_limit=3
</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><option>logfile</option>=<replaceable>file_name</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>file_name</replaceable> is an absolute path to the file in which <command>dnf</command> should write its logging output. By default, <command>dnf</command> logs to <filename>/var/log/dnf.log</filename>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>multilib_policy</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>best</literal> — install the best-choice architecture for this system. For example, setting <option>multilib_policy=best</option> on an AMD64 system causes <command>dnf</command> to install 64-bit versions of all packages.
- </para>
- <para>
- <literal>all</literal> — always install every possible architecture for every package. For example, with <option>multilib_policy</option> set to <literal>all</literal> on an AMD64 system, <command>dnf</command> would install both the i586 and AMD64 versions of a package, if both were available.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>obsoletes</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>0</literal> — Disable <command>dnf</command>'s obsoletes processing logic when performing updates.
- </para>
- <para>
- <literal>1</literal> — Enable <command>dnf</command>'s obsoletes processing logic when performing updates. When one package declares in its spec file that it <firstterm>obsoletes</firstterm> another package, the latter package will be replaced by the former package when the former package is installed. Obsoletes are declared, for example, when a package is renamed. <option>obsoletes=1</option> the default.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>plugins</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is one of:
- </para>
- <para>
- <literal>0</literal> — Disable all DNF plug-ins globally.
- </para>
- <important id="important-Disabling_all_plugins_is_not_advised-main_options">
- <title>Disabling all plug-ins is not advised</title>
- <para>
- Disabling all plug-ins is not advised because certain plug-ins provide important <command>DNF</command> services. Disabling plug-ins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <command>DNF</command>.
- </para>
- </important>
- <para>
- <literal>1</literal> — Enable all DNF plug-ins globally. With <option>plugins=1</option>, you can still disable a specific DNF plug-in by setting <option>enabled=0</option> in that plug-in's configuration file.
- </para>
- <para>
- For more information about various DNF plug-ins, refer to <xref linkend="sec-DNF_Plugins" />. For further information on controlling plug-ins, see <xref linkend="sec-Enabling_Configuring_and_Disabling_DNF_Plugins" />.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>reposdir</option>=<replaceable>directory</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>directory</replaceable> is an absolute path to the directory where <filename class="extension">.repo</filename> files are located. All <filename class="extension">.repo</filename> files contain repository information (similar to the <literal>[<replaceable>repository</replaceable>]</literal> sections of <filename>/etc/dnf.conf</filename>). <command>dnf</command> collects all repository information from <filename class="extension">.repo</filename> files and the <literal>[<replaceable>repository</replaceable>]</literal> section of the <filename>/etc/dnf.conf</filename> file to create a master list of repositories to use for transactions. If <literal>reposdir</literal> is not set, <command>dnf</command> uses the default directory <filename class="directory">/etc/dnf.repos.d/</filename>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>retries</option>=<replaceable>value</replaceable></term>
- <listitem>
- <para>
- …where <replaceable>value</replaceable> is an integer <literal>0</literal> or greater. This value sets the number of times <command>dnf</command> should attempt to retrieve a file before returning an error. Setting this to <literal>0</literal> makes <command>dnf</command> retry forever. The default value is <literal>10</literal>.
- </para>
- </listitem>
- </varlistentry>
</variablelist>
<para>
- For a complete list of available <literal>[main]</literal> options, refer to the <literal>[main] OPTIONS</literal> section of the <emphasis role="bold">dnf.conf</emphasis>(5) manual page.
+ For a complete list of available <literal>[main]</literal> options, refer to the <literal>[MAIN] OPTIONS</literal> section of the <emphasis role="bold">dnf.conf</emphasis>(5) manual page.
</para>
</section>
<section id="sec-Setting_repository_Options">
@@ -1498,7 +1214,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<term><option>baseurl</option>=<replaceable>repository_url</replaceable></term>
<listitem>
<para>
- …where <replaceable>repository_url</replaceable> is a URL to the directory where the repodata directory of a repository is located:
+ …where <replaceable>repository_url</replaceable> is a URL to the directory where the <filename class="directory">repodata</filename> directory of a repository is located:
</para>
<itemizedlist>
<listitem>
@@ -1518,7 +1234,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
</listitem>
<listitem>
<para>
- If a specific online repository requires basic HTTP authentication, you can specify your username and password by prepending it to the URL as <option><replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>link</replaceable></option>. For example, if a repository on http://www.example.com/repo/ requires a username of <quote>user</quote> and a password of <quote>password</quote>, then the <option>baseurl</option> link could be specified as <option>http://<userinput>user</userinput>:<userinput>password</userinput>@www.example.com/repo/</option>.
+ If a specific online repository requires basic HTTP authentication, you can specify your user name and password by prepending it to the URL as <option><replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>link</replaceable></option>. For example, if a repository on http://www.example.com/repo/ requires a username of <quote>user</quote> and a password of <quote>password</quote>, then the <option>baseurl</option> link could be specified as <option>http://<userinput>user</userinput>:<userinput>password</userinput>@www.example.com/repo/</option>.
</para>
</listitem>
</itemizedlist>
@@ -1549,7 +1265,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<literal>1</literal> — Include this repository as a package source.
</para>
<para>
- Turning repositories on and off can also be performed by passing either the <option>--enablerepo=<replaceable>repo_name</replaceable></option> or <option>--disablerepo=<replaceable>repo_name</replaceable></option> option to <command>dnf</command>, or through the <guilabel>Add/Remove Software</guilabel> window of the <application>PackageKit</application> utility.
+ Turning repositories on and off can also be performed by passing either the <option>--enablerepo=<replaceable>repo_name</replaceable></option> or <option>--disablerepo=<replaceable>repo_name</replaceable></option> option to the <command>dnf</command> cpmmand, or through the <guilabel>Add/Remove Software</guilabel> window of the <application>PackageKit</application> utility.
</para>
</listitem>
</varlistentry>
@@ -1565,14 +1281,14 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<secondary>variables</secondary>
</indexterm>
<para>
- You can use and reference the following built-in variables in <command>dnf</command> commands and in all DNF configuration files (that is, <filename>/etc/dnf.conf</filename> and all <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/dnf.repos.d/</filename> directory):
+ You can use and reference the following built-in variables in <command>dnf</command> commands and in all DNF configuration files (that is, <filename>/etc/dnf/dnf.conf</filename> and all <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename> directory):
</para>
<variablelist>
<varlistentry>
<term><varname>$releasever</varname></term>
<listitem>
<para>
- You can use this variable to reference the release version of &MAJOROS;. DNF obtains the value of <varname>$releasever</varname> from the <literal>distroverpkg=<replaceable>value</replaceable></literal> line in the <filename>/etc/dnf.conf</filename> configuration file. If there is no such line in <filename>/etc/dnf.conf</filename>, then <command>dnf</command> infers the correct value by deriving the version number from the <package>redhat-release</package> package.
+ You can use this variable to reference the release version of &MAJOROS;. DNF obtains the value of <varname>$releasever</varname> from the <literal>distroverpkg=<replaceable>value</replaceable></literal> line in the <filename>/etc/dnf/dnf.conf</filename> configuration file. If there is no such line in <filename>/etc/dnf/dnf.conf</filename>, then <command>dnf</command> infers the correct value by deriving the version number from the <package>redhat-release</package> package.
</para>
</listitem>
</varlistentry>
@@ -1596,7 +1312,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<term><varname>$YUM0-9</varname></term>
<listitem>
<para>
- These ten variables are each replaced with the value of any shell environment variables with the same name. If one of these variables is referenced (in <filename>/etc/dnf.conf</filename> for example) and a shell environment variable with the same name does not exist, then the configuration file variable is not replaced.
+ These ten variables are each replaced with the value of any shell environment variables with the same name. If one of these variables is referenced (in <filename>/etc/dnf/dnf.conf</filename> for example) and a shell environment variable with the same name does not exist, then the configuration file variable is not replaced.
</para>
</listitem>
</varlistentry>
@@ -1613,645 +1329,8 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
</para>
<programlisting>name=$osname $releasever</programlisting>
</section>
- <section id="sec-Viewing_the_Current_Configuration">
- <title>Viewing the Current Configuration</title>
- <para>
- To display the current values of global DNF options (that is, the options specified in the <literal>[main]</literal> section of the <filename>/etc/dnf.conf</filename> file), run the <command>dnf-config-manager</command> with no command line options:
- </para>
- <synopsis><command>dnf-config-manager</command></synopsis>
- <para>
- To list the content of a different configuration section or sections, use the command in the following form:
- </para>
- <synopsis><command>dnf-config-manager</command> <replaceable>section</replaceable>…</synopsis>
- <para>
- You can also use a glob expression to display the configuration of all matching sections:
- </para>
- <synopsis><command>dnf-config-manager</command> <replaceable>glob_expression</replaceable>…</synopsis>
- <para>
- For example, to list all configuration options and their corresponding values, type the following at a shell prompt:
- </para>
- <screen>~]$ <command>dnf-config-manager main \*</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-================================== main ===================================
-[main]
-alwaysprompt = True
-assumeyes = False
-bandwith = 0
-bugtracker_url = https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%...
-cache = 0
-<lineannotation>[output truncated]</lineannotation></screen>
- </section>
- <section id="sec-Managing_DNF_Repositories">
- <title>Adding, Enabling, and Disabling a DNF Repository</title>
- <indexterm>
- <primary>DNF</primary>
- <secondary>repository</secondary>
- </indexterm>
- <para>
- <xref linkend="sec-Setting_repository_Options" /> described various options you can use to define a DNF repository. This section explains how to add, enable, and disable a repository by using the <command>dnf-config-manager</command> command.
- </para>
- <bridgehead id="bh-Managing_DNF_Repositories-Adding">
- Adding a DNF Repository
- </bridgehead>
- <para>
- To define a new repository, you can either add a <literal>[<replaceable>repository</replaceable>]</literal> section to the <filename>/etc/dnf.conf</filename> file, or to a <filename class="extension">.repo</filename> file in the <filename class="directory">/etc/dnf.repos.d/</filename> directory. All files with the <filename class="extension">.repo</filename> file extension in this directory are read by <command>dnf</command>, and best practice is to define your repositories here instead of in <filename>/etc/dnf.conf</filename>.
- </para>
- <warning>
- <title>Be careful when using untrusted software sources</title>
- <para>
- Obtaining and installing software packages from unverified or untrusted software sources constitutes a potential security risk, and could lead to security, stability, compatibility maintainability issues.
- </para>
- </warning>
- <para>
- DNF repositories commonly provide their own <filename class="extension">.repo</filename> file. To add such a repository to your system and enable it, run the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf-config-manager</command> <option>--add-repo</option> <replaceable>repository_url</replaceable></synopsis>
- <para>
- …where <replaceable>repository_url</replaceable> is a link to the <filename class="extension">.repo</filename> file. For example, to add a repository located at http://www.example.com/example.repo, type the following at a shell prompt:
- </para>
- <screen>~]# <command>dnf-config-manager --add-repo http://www.example.com/example.repo</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-adding repo from: http://www.example.com/example.repo
-grabbing file http://www.example.com/example.repo to /etc/dnf.repos.d/example.repo
-example.repo | 413 B 00:00
-repo saved to /etc/dnf.repos.d/example.repo</screen>
- <bridgehead id="bh-Managing_DNF_Repositories-Enabling">
- Enabling a DNF Repository
- </bridgehead>
- <para>
- To enable a particular repository or repositories, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf-config-manager</command> <option>--enable</option> <replaceable>repository</replaceable>…</synopsis>
- <para>
- …where <replaceable>repository</replaceable> is the unique repository ID (use <command>dnf repolist all</command> to list available repository IDs). Alternatively, you can use a glob expression to enable all matching repositories:
- </para>
- <synopsis><command>dnf-config-manager</command> <option>--enable</option> <replaceable>glob_expression</replaceable>…</synopsis>
- <para>
- For example, to disable repositories defined in the <literal>[example]</literal>, <literal>[example-debuginfo]</literal>, and <literal>[example-source]</literal>sections, type:
- </para>
- <screen>~]# <command>dnf-config-manager --enable example\*</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-============================== repo: example ==============================
-[example]
-bandwidth = 0
-base_persistdir = /var/lib/dnf/repos/x86_64/6Server
-baseurl = http://www.example.com/repo/6Server/x86_64/
-cache = 0
-cachedir = /var/cache/dnf/x86_64/6Server/example
-<lineannotation>[output truncated]</lineannotation></screen>
- <para>
- When successful, the <command>dnf-config-manager --enable</command> command displays the current repository configuration.
- </para>
- <bridgehead id="bh-Managing_DNF_Repositories-Disabling">
- Disabling a DNF Repository
- </bridgehead>
- <para>
- To disable a DNF repository, run the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>dnf-config-manager</command> <option>--disable</option> <replaceable>repository</replaceable>…</synopsis>
- <para>
- …where <replaceable>repository</replaceable> is the unique repository ID (use <command>dnf repolist all</command> to list available repository IDs). Similarly to <command>dnf-config-manager --enable</command>, you can use a glob expression to disable all matching repositories at the same time:
- </para>
- <synopsis><command>dnf-config-manager</command> <option>--disable</option> <replaceable>glob_expression</replaceable>…</synopsis>
- <para>
- When successful, the <command>dnf-config-manager --disable</command> command displays the current configuration.
- </para>
- </section>
- <section id="sec-Creating_a_DNF_Repository">
- <title>Creating a DNF Repository</title>
- <indexterm>
- <primary>DNF</primary>
- <secondary>repository</secondary>
- </indexterm>
- <para>
- To set up a DNF repository, follow these steps:
- </para>
- <procedure id="procedure-Setting_Up_a_DNF_repository">
- <step>
- <para>
- Install the <package>createrepo</package> package:
- </para>
- <screen>~]# <command>dnf install createrepo</command></screen>
- </step>
- <step>
- <para>
- Copy all of the packages into one directory, such as <filename class="directory">/mnt/local_repo/</filename>.
- </para>
- </step>
- <step>
- <para>
- Run the <command>createrepo --database</command> command on that directory:
- </para>
- <screen>~]# <command>createrepo --database /mnt/local_repo</command></screen>
- </step>
- </procedure>
- <para>
- This creates the necessary metadata for your DNF repository, as well as the <application>sqlite</application> database for speeding up <command>dnf</command> operations.
- </para>
- </section>
</section>
- <section id="sec-DNF_Plugins">
- <title>DNF Plug-ins</title>
- <indexterm>
- <primary>DNF</primary>
- <secondary>DNF plug-ins</secondary>
- </indexterm>
- <para>
- DNF provides plug-ins that extend and enhance its operations. Certain plug-ins are installed by default. DNF always informs you which plug-ins, if any, are loaded and active whenever you call any <command>dnf</command> command. For example:
- </para>
- <screen>~]# <command>dnf info dnf</command>
-Loaded plugins: langpacks, presto, refresh-packagekit
-<lineannotation>[output truncated]</lineannotation></screen>
- <para>
- Note that the plug-in names which follow <command>Loaded plugins</command> are the names you can provide to the <option>--disableplugin=<replaceable>plugin_name</replaceable></option> option.
- </para>
- <section id="sec-Enabling_Configuring_and_Disabling_DNF_Plugins">
- <title>Enabling, Configuring, and Disabling DNF Plug-ins</title>
- <indexterm>
- <primary>DNF</primary>
- <secondary>enabling plug-ins</secondary>
- </indexterm>
- <indexterm>
- <primary>DNF</primary>
- <secondary>configuring plug-ins</secondary>
- </indexterm>
- <indexterm>
- <primary>DNF</primary>
- <secondary>disabling plug-ins</secondary>
- </indexterm>
- <para>
- To enable DNF plug-ins, ensure that a line beginning with <command>plugins=</command> is present in the <literal>[main]</literal> section of <filename>/etc/dnf.conf</filename>, and that its value is set to <literal>1</literal>:
- </para>
- <programlisting>plugins=1</programlisting>
- <para>
- You can disable all plug-ins by changing this line to <command>plugins=0</command>.
- </para>
- <important id="important-Disabling_all_plugins_is_not_advised-plugins">
- <title>Disabling all plug-ins is not advised</title>
- <para>
- Disabling all plug-ins is not advised because certain plug-ins provide important <command>DNF</command> services. Disabling plug-ins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <command>DNF</command>.
- </para>
- </important>
- <para>
- Every installed plug-in has its own configuration file in the <filename class="directory">/etc/dnf/pluginconf.d/</filename> directory. You can set plug-in specific options in these files. For example, here is the <application>refresh-packagekit</application> plug-in's <filename>refresh-packagekit.conf</filename> configuration file:
- </para>
- <programlisting>[main]
-enabled=1</programlisting>
- <para>
- Plug-in configuration files always contain a <literal>[main]</literal> section (similar to DNF's <filename>/etc/dnf.conf</filename> file) in which there is (or you can place if it is missing) an <literal>enabled=</literal> option that controls whether the plug-in is enabled when you run <command>dnf</command> commands.
- </para>
- <para>
- If you disable all plug-ins by setting <command>enabled=0</command> in <filename>/etc/dnf.conf</filename>, then all plug-ins are disabled regardless of whether they are enabled in their individual configuration files.
- </para>
- <para>
- If you merely want to disable all DNF plug-ins for a single <command>dnf</command> command, use the <option>--noplugins</option> option.
- </para>
- <para>
- If you want to disable one or more DNF plug-ins for a single <command>dnf</command> command, add the <option>--disableplugin=<replaceable>plugin_name</replaceable></option> option to the command. For example, to disable the <application>presto</application> plug-in while updating a system, type:
- </para>
- <screen>~]# <command>dnf update --disableplugin=presto</command></screen>
- <para>
- The plug-in names you provide to the <option>--disableplugin=</option> option are the same names listed after the <command>Loaded plugins</command> line in the output of any <command>dnf</command> command. 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:
- </para>
- <screen>~]# <command>dnf update --disableplugin=presto,refresh-pack*</command></screen>
- </section>
- <section id="sec-Installing_More_DNF_Plugins">
- <title>Installing Additional DNF Plug-ins</title>
- <para>
- DNF plug-ins usually adhere to the <filename>dnf-plugin-<replaceable>plugin_name</replaceable></filename> package-naming convention, but not always: the package which provides the <application>presto</application> plug-in is named <filename>dnf-presto</filename>, for example. You can install a DNF plug-in in the same way you install other packages. For instance, to install the <application>security</application> plug-in, type the following at a shell prompt:
- </para>
- <screen>~]# <command>dnf install dnf-plugin-security</command></screen>
- </section>
- <section id="sec-Plugin_Descriptions">
- <title>Plug-in Descriptions</title>
- <para>
- The following list provides descriptions of a few useful DNF plug-ins:
- </para>
- <variablelist>
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>fs-snapshot</application></tertiary>
- </indexterm>
- <application>fs-snapshot</application> (<package>dnf-plugin-fs-snapshot</package>)
- </term>
- <listitem>
- <para>
- The <application>fs-snapshot</application> plug-in extends DNF to create a snapshot of a file system before proceeding with a transaction such as a system update or package removal. When a user decides that the changes made by the transaction are unwanted, this mechanism allows the user to roll back to the changes that are stored in a snapshot.
- </para>
- <para>
- In order for the plug-in to work, the root file system (that is, <filename class="directory">/</filename>) must be on an <systemitem class="filesystem">LVM</systemitem> (Logical Volume Manager) or <systemitem class="filesystem">Btrfs</systemitem> volume.
- To use the <application>fs-snapshot</application> plug-in on an LVM volume, take the following steps:
- </para>
- <procedure>
- <step>
- <para>
- Make sure that the volume group with the root file system has enough free extents. The required size is a function of the amount of changes to the original logical volume that is expected during the life of the snapshot. The reasonable default is 50–80 % of the original logical volume size.
- </para>
- <para>
- To display detailed information about a particular volume group, run the <command>vgdisplay</command> command in the following form as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>vgdisplay</command> <replaceable>volume_group</replaceable></synopsis>
- <para>
- The number of free extents is listed on the <literal>Free PE / Size</literal> line.
- </para>
- </step>
- <step performance="optional">
- <para>
- If the volume group with the root file system does not have enough free extents, add a new physical volume:
- </para>
- <substeps>
- <step>
- <para>
- As <systemitem class="username">root</systemitem>, run the <command>pvcreate</command> command in the following form to initialize a physical volume for use with the Logical Volume Manager:
- </para>
- <synopsis><command>pvcreate</command> <replaceable>device</replaceable></synopsis>
- </step>
- <step>
- <para>
- Use the <command>vgextend</command> command in the following form as <systemitem class="username">root</systemitem> to add the physical volume to the volume group:
- </para>
- <synopsis><command>vgextend</command> <replaceable>volume_group</replaceable> <replaceable>physical_volume</replaceable></synopsis>
- </step>
- </substeps>
- </step>
- <step>
- <para>
- Edit the configuration file located in <filename>/etc/dnf/pluginconf.d/fs-snapshot.conf</filename>, and make the following changes to the <literal>[lvm]</literal> section:
- </para>
- <substeps>
- <step>
- <para>
- Change the value of the <option>enabled</option> option to <literal>1</literal>:
- </para>
- <programlisting>enabled = 1</programlisting>
- </step>
- <step>
- <para>
- Remove the hash sign (that is, <literal>#</literal>) from the beginning of the <option>lvcreate_size_args</option> line, and adjust the number of logical extents to be allocated for a snapshot. For example, to allocate 80 % of the size of the original logical volume, use:
- </para>
- <programlisting>lvcreate_size_args = -l 80%ORIGIN</programlisting>
- </step>
- </substeps>
- <para>
- See <xref linkend="tabl-DNF-Plugin_Descriptions-fs-snapshot" /> for a complete list of available configuration options.
- </para>
- </step>
- <step>
- <para>
- Run the desired <command>dnf</command> command, and make sure <application>fs-snapshot</application> is included in the list of loaded plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the changes and proceed with the transaction. The <application>fs-snapshot</application> plug-in displays a line in the following form for each affected logical volume:
- </para>
- <synopsis>fs-snapshot: snapshotting <replaceable>file_system</replaceable> (/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>): <replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
- </step>
- <step>
- <para>
- Verify that the system is working as expected:
- </para>
- <stepalternatives>
- <step>
- <para>
- If you decide to keep the changes, remove the snapshot by running the <command>lvremove</command> command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>lvremove</command> /dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
- </step>
- <step>
- <para>
- If you decide to revert the changes and restore the file system to a state that is saved in a snapshot, take the following steps:
- </para>
- <substeps>
- <step>
- <para>
- As <systemitem class="username">root</systemitem>, run the command in the following form to merge a snapshot into its original logical volume:
- </para>
- <synopsis><command>lvconvert</command> <option>--merge</option> /dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
- <para>
- The <command>lvconvert</command> command will inform you that a restart is required in order for the changes to take effect.
- </para>
- </step>
- <step>
- <para>
- Restart the system as instructed. You can do so by typing the following at a shell prompt as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>reboot</command></synopsis>
- </step>
- </substeps>
- </step>
- </stepalternatives>
- </step>
- </procedure>
- <para>
- To use the <application>fs-snapshot</application> plug-in on a Btrfs file system, take the following steps:
- </para>
- <procedure>
- <step>
- <para>
- Run the desired <command>dnf</command> command, and make sure <application>fs-snapshot</application> is included in the list of loaded plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the changes and proceed with the transaction. The <application>fs-snapshot</application> plug-in displays a line in the following form for each affected file system:
- </para>
- <synopsis>fs-snapshot: snapshotting <replaceable>file_system</replaceable>: <replaceable>file_system</replaceable>/dnf_<replaceable>timestamp</replaceable></synopsis>
- </step>
- <step>
- <para>
- Verify that the system is working as expected:
- </para>
- <stepalternatives>
- <step performance="optional">
- <para>
- If you decide to keep the changes, you can optionally remove unwanted snapshots. To remove a Btrfs snapshot, use the command in the following form as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>btrfs</command> <option>subvolume</option> <option>delete</option> <replaceable>file_system</replaceable>/dnf_<replaceable>timestamp</replaceable></synopsis>
- </step>
- <step>
- <para>
- If you decide to revert the changes and restore a file system to a state that is saved in a snapshot, take the following steps:
- </para>
- <substeps>
- <step>
- <para>
- Determine the identifier of a particular snapshot by using the following command as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>btrfs</command> <option>subvolume</option> <option>list</option> <replaceable>file_system</replaceable></synopsis>
- </step>
- <step>
- <para>
- As <systemitem class="username">root</systemitem>, configure the system to mount this snapshot by default:
- </para>
- <synopsis><command>btrfs</command> <option>subvolume</option> <option>set-default</option> <replaceable>id</replaceable> <replaceable>file_system</replaceable></synopsis>
- </step>
- <step>
- <para>
- Restart the system. You can do so by typing the following at a shell prompt as <systemitem class="username">root</systemitem>:
- </para>
- <synopsis><command>reboot</command></synopsis>
- </step>
- </substeps>
- </step>
- </stepalternatives>
- </step>
- </procedure>
- <para>
- For more information on logical volume management, Btrfs, and file system snapshots, see the <ulink url="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storag..."><citetitle pubwork="book">&MAJOROSVER; Storage Administration Guide</citetitle></ulink>. For additional information about the plug-in and its configuration, refer to the <emphasis role="bold">dnf-fs-snapshot</emphasis>(1) and <emphasis role="bold">dnf-fs-snapshot.conf</emphasis>(5) manual pages.
- </para>
- <table id="tabl-DNF-Plugin_Descriptions-fs-snapshot">
- <title>Supported <filename>fs-snapshot.conf</filename> directives</title>
- <tgroup cols="3">
- <colspec colname="section" colnum="1" colwidth="15*" />
- <colspec colname="directive" colnum="2" colwidth="35*" />
- <colspec colname="description" colnum="3" colwidth="50*" />
- <thead>
- <row>
- <entry>
- Section
- </entry>
- <entry>
- Directive
- </entry>
- <entry>
- Description
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry morerows="1" valign="middle">
- <literal>[main]</literal>
- </entry>
- <entry>
- <option>enabled</option>=<replaceable>value</replaceable>
- </entry>
- <entry>
- Allows you to enable or disable the plug-in. The <replaceable>value</replaceable> must be either <literal>1</literal> (enabled), or <literal>0</literal> (disabled). When installed, the plug-in is enabled by default.
- </entry>
- </row>
- <row>
- <entry>
- <option>exclude</option>=<replaceable>list</replaceable>
- </entry>
- <entry>
- Allows you to exclude certain file systems. The value must be a space-separated <replaceable>list</replaceable> of mount points you do <emphasis>not</emphasis> want to snapshot (for example, <literal>/srv /mnt/backup</literal>). This option is not included in the configuration file by default.
- </entry>
- </row>
- <row>
- <entry morerows="1" valign="middle">
- <literal>[lvm]</literal>
- </entry>
- <entry>
- <option>enabled</option>=<replaceable>value</replaceable>
- </entry>
- <entry>
- Allows you to enable or disable the use of the plug-in on LVM volumes. The <replaceable>value</replaceable> must be either <literal>1</literal> (enabled), or <literal>0</literal> (disabled). This option is disabled by default.
- </entry>
- </row>
- <row>
- <entry>
- <option>lvcreate_size_args</option>=<replaceable>value</replaceable>
- </entry>
- <entry>
- Allows you to specify the size of a logical volume snapshot. The <replaceable>value</replaceable> must be the <option>-l</option> or <option>-L</option> command line option for the <application>lvcreate</application> utility followed by a valid argument (for example, <literal>-l 80%ORIGIN</literal>).
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </listitem>
- </varlistentry>
- <!-- jhradile: This plug-in is not available for Fedora 15.
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>kabi</application></tertiary>
- </indexterm>
- <application>kabi</application> (<package>kabi-dnf-plugins</package>)
- </term>
- <listitem>
- <para>
- The <application>kabi</application> plug-in checks whether a driver update package conforms with official &OSORG; <firstterm>kernel Application Binary Interface</firstterm> (<acronym>kABI</acronym>). With this plug-in enabled, when a user attempts to install a package that uses kernel symbols which are not on a whitelist, a warning message is written to the system log. Additionally, configuring the plug-in to run in enforcing mode prevents such packages from being installed at all.
- </para>
- <para>
- To configure the <application>kabi</application> plug-in, edit the configuration file located in <filename>/etc/dnf/pluginconf.d/kabi.conf</filename>. See <xref linkend="tabl-DNF-Plugin_Descriptions-kabi" /> for a list of directives that can be used in the <option>[main]</option> section.
- </para>
- <table id="tabl-DNF-Plugin_Descriptions-kabi">
- <title>Supported <filename>kabi.conf</filename> directives</title>
- <tgroup cols="2">
- <colspec colname="directive" colnum="1" colwidth="30*" />
- <colspec colname="description" colnum="2" colwidth="70*" />
- <thead>
- <row>
- <entry>
- Directive
- </entry>
- <entry>
- Description
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <option>enabled</option>=<replaceable>value</replaceable>
- </entry>
- <entry>
- Allows you to enable or disable the plug-in. The <replaceable>value</replaceable> must be either <literal>1</literal> (enabled), or <literal>0</literal> (disabled). When installed, the plug-in is enabled by default.
- </entry>
- </row>
- <row>
- <entry>
- <option>whitelists</option>=<replaceable>directory</replaceable>
- </entry>
- <entry>
- Allows you to specify the <replaceable>directory</replaceable> in which the files with supported kernel symbols are located. By default, the <application>kabi</application> plug-in uses files provided by the <package>kabi-whitelists</package> package (that is, the <filename class="directory">/lib/modules/kabi/</filename> directory).
- </entry>
- </row>
- <row>
- <entry>
- <option>enforce</option>=<replaceable>value</replaceable>
- </entry>
- <entry>
- Allows you to enable or disable enforcing mode. The <replaceable>value</replaceable> must be either <literal>1</literal> (enabled), or <literal>0</literal> (disabled). By default, this option is commented out and the <application>kabi</application> plug-in only displays a warning message.
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </listitem>
- </varlistentry>
- -->
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>presto</application></tertiary>
- </indexterm>
- <application>presto</application> (<package>dnf-presto</package>)
- </term>
- <listitem>
- <para>
- The <application>presto</application> plug-in adds support to DNF for downloading <firstterm>delta RPM</firstterm> packages, during updates, from repositories which have <application>presto</application> metadata enabled. Delta RPMs contain only the differences between the version of the package installed on the client requesting the RPM package and the updated version in the repository.
- </para>
- <para>
- Downloading a delta RPM is much quicker than downloading the entire updated package, and can speed up updates considerably. Once the delta RPMs are downloaded, they must be rebuilt to apply the difference to the currently-installed package and thus create the full, updated package. This process takes CPU time on the installing machine. Using delta RPMs is therefore a tradeoff between time-to-download, which depends on the network connection, and time-to-rebuild, which is CPU-bound. Using the <application>presto</application> plug-in is recommended for fast machines and systems with slower network connections, while slower machines on very fast connections <emphasis>may</emphasis> benefit more from downloading normal RPM packages, that is, by disabling <application>presto</application>.
- </para>
- </listitem>
- </varlistentry>
- <!-- jhradile: This plug-in is not available for Fedora 15.
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>protect-packages</application></tertiary>
- </indexterm>
- <application>protect-packages</application> (<package>dnf-plugin-protect-packages</package>)
- </term>
- <listitem>
- <para>
- The <application>protect-packages</application> plug-in prevents the <package>dnf</package> package and all packages it depends on from being deliberately or accidentally removed. This prevents many of the most important packages necessary for your system to run from being removed. In addition, you can list more packages, one per line, in the <filename>/etc/sysconfig/protected-packages</filename> file<footnote id="footnote-Alternative_Locations_for_protect-packages_Lists"><para>You can also place files with the extension <filename class="extension">.list</filename> in the <filename class="directory">/etc/sysconfig/protected-packages.d/</filename> directory (which you should create if it does not exist), and list packages—one per line—in these files. <application>protect-packages</application> will protect these too.</para></footnote> (which you should create if it does not exist), and <application>protect-packages</application> will extend protection-from-r
emoval to those packages as well.
- </para>
- <para>
- To temporarily override package protection, use the <option>- -override-protection</option> option with an applicable <command>dnf</command> command.
- </para>
- </listitem>
- </varlistentry>
- -->
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>refresh-packagekit</application></tertiary>
- </indexterm>
- <application>refresh-packagekit</application> (<package>PackageKit-dnf-plugin</package>)
- </term>
- <listitem>
- <para>
- The <application>refresh-packagekit</application> plug-in updates metadata for <application>PackageKit</application> whenever <command>dnf</command> is run. The <application>refresh-packagekit</application> plug-in is installed by default.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>rhnplugin</application></tertiary>
- </indexterm>
- <application>rhnplugin</application> (<package>dnf-rhn-plugin</package>)
- </term>
- <listitem>
- <para>
- The <application>rhnplugin</application> provides support for connecting to <systemitem class="systemname">RHN Classic</systemitem>. This allows systems registered with <systemitem class="systemname">RHN Classic</systemitem> to update and install packages from this system.
- </para>
- <para>
- See the <emphasis role="bold">rhnplugin</emphasis>(8) manual page for more information about the plug-in.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <indexterm>
- <primary>DNF</primary>
- <secondary>plug-ins</secondary>
- <tertiary><application>security</application></tertiary>
- </indexterm>
- <application>security</application> (<package>dnf-plugin-security</package>)
- </term>
- <listitem>
- <para>
- Discovering information about and applying security updates easily and often is important to all system administrators. For this reason DNF provides the <application>security</application> plug-in, which extends <command>dnf</command> with a set of highly-useful security-related commands, subcommands and options.
- </para>
- <para>
- You can check for security-related updates as follows:
- </para>
- <screen>~]# <command>dnf check-update --security</command>
-Loaded plugins: langpacks, presto, refresh-packagekit, security
-Limiting package lists to security relevant ones
-updates-testing/updateinfo | 329 kB 00:00
-9 package(s) needed for security, out of 270 available
-ConsoleKit.x86_64 0.4.5-1.fc15 updates
-ConsoleKit-libs.x86_64 0.4.5-1.fc15 updates
-ConsoleKit-x11.x86_64 0.4.5-1.fc15 updates
-NetworkManager.x86_64 1:0.8.999-2.git20110509.fc15 updates
-NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
-<lineannotation>[output truncated]</lineannotation></screen>
- <para>
- You can then use either <command>dnf update --security</command> or <command>dnf update-minimal --security</command> to update those packages which are affected by security advisories. Both of these commands update all packages on the system for which a security advisory has been issued. <command>dnf update-minimal --security</command> updates them to the latest packages which were released as part of a security advisory, while <command>dnf update --security</command> will update all packages affected by a security advisory <emphasis>to the latest version of that package available</emphasis>.
- </para>
- <para>
- In other words, if:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- the <package>kernel-2.6.38.4-20</package> package is installed on your system;
- </para>
- </listitem>
- <listitem>
- <para>
- the <package>kernel-2.6.38.6-22</package> package was released as a security update;
- </para>
- </listitem>
- <listitem>
- <para>
- then <package>kernel-2.6.38.6-26</package> was released as a bug fix update,
- </para>
- </listitem>
- </itemizedlist>
- <para>
- ...then <command>dnf update-minimal --security</command> will update you to <package>kernel-2.6.38.6-22</package>, and <command>dnf update --security</command> will update you to <package>kernel-2.6.38.6-26</package>. Conservative system administrators may want to use <command>update-minimal</command> to reduce the risk incurred by updating packages as much as possible.
- </para>
- <para>
- See the <emphasis role="bold">dnf-security</emphasis>(8) manual page for usage details and further explanation of the enhancements the <application>security</application> plug-in adds to <command>dnf</command>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- </section>
<section id="sec-Additional_Resources">
<title>Additional Resources</title>
<indexterm>
@@ -2261,11 +1340,11 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
<variablelist>
<varlistentry>
<term>
- <ulink url="http://dnf.baseurl.org/wiki/Guides" />
+ <ulink url="http://dnf.readthedocs.org/en/latest/index.html" />
</term>
<listitem>
<para>
- The <literal>DNF Guides</literal> section of the DNF wiki contains more documentation.
+ The DNF wiki contains more documentation.
</para>
</listitem>
</varlistentry>
9 years
[system-administrators-guide] Change Yum to DNF in RPM.xml
by stephenw
commit 63bef7b3d4259b22d31db2d5b8483a2e53034e7b
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Fri Apr 17 17:08:47 2015 +0200
Change Yum to DNF in RPM.xml
en-US/RPM.xml | 20 ++++++++++----------
1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index 35fb303..511b7df 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -19,19 +19,19 @@
The <firstterm>RPM Package Manager</firstterm> (<application>RPM</application>) is an open packaging system that runs on &MAJOROS; as well as other Linux and UNIX systems. Red Hat and the Fedora Project encourage other vendors to use <application>RPM</application> for their own products. <application>RPM</application> is distributed under the terms of the <firstterm>GPL</firstterm> (<firstterm>GNU General Public License</firstterm>).
</para>
<para>
- The <application>RPM Package Manager</application> only works with packages built in the <emphasis>RPM format</emphasis>. <application>RPM</application> itself is provided as the pre-installed <package>rpm</package> package. For the end user, <application>RPM</application> makes system updates easy. Installing, uninstalling, and upgrading <application>RPM</application> packages can be accomplished with short commands. <application>RPM</application> maintains a database of installed packages and their files, so you can make queries and verify installed files on your system. There are several applications, such as <application>Yum</application> or <application>PackageKit</application>, that can make working with packages in the <application>RPM</application> format even easier.
+ The <application>RPM Package Manager</application> only works with packages built in the <emphasis>RPM format</emphasis>. <application>RPM</application> itself is provided as the pre-installed <package>rpm</package> package. For the end user, <application>RPM</application> makes system updates easy. Installing, uninstalling, and upgrading <application>RPM</application> packages can be accomplished with short commands. <application>RPM</application> maintains a database of installed packages and their files, so you can make queries and verify installed files on your system. There are several applications, such as <application>DNF</application> or <application>PackageKit</application>, that can make working with packages in the <application>RPM</application> format even easier.
</para>
- <warning id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible">
- <title>Use Yum Instead of RPM Whenever Possible</title>
+ <warning id="warning-Use_DNF_Instead_of_RPM_Whenever_Possible">
+ <title>Use DNF Instead of RPM Whenever Possible</title>
<indexterm>
<primary>packages</primary>
- <secondary>Yum instead of RPM</secondary>
+ <secondary>DNF instead of RPM</secondary>
</indexterm>
<para>
- For most package-management tasks, the <application>Yum</application> package manager offers equal and often greater capabilities and utility than <application>RPM</application>. <application>Yum</application> also performs and tracks complicated system-dependency resolutions. <application>Yum</application> maintains the system integrity and forces a system integrity check if packages are installed or removed using another application, such as <application>RPM</application>, instead of <application>Yum</application>. For these reasons, it is highly recommended that you use <application>Yum</application> instead of <application>RPM</application> whenever possible to perform package-management tasks. See <xref linkend="ch-yum"/>.
+ For most package-management tasks, the <application>DNF</application> package manager offers equal and often greater capabilities and utility than <application>RPM</application>. <application>DNF</application> also performs and tracks complicated system-dependency resolutions. <application>DNF</application> maintains the system integrity and forces a system integrity check if packages are installed or removed using another application, such as <application>RPM</application>, instead of <application>DNF</application>. For these reasons, it is highly recommended that you use <application>DNF</application> instead of <application>RPM</application> whenever possible to perform package-management tasks. See <xref linkend="ch-DNF"/>.
</para>
<para>
- If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>Yum</application> as its back end, to manage your system's packages.
+ If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>DNF</application> as its back end, to manage your system's packages.
</para>
</warning>
<para>
@@ -298,7 +298,7 @@
<warning id="warning-Forcing_Package_Installation">
<title>Warning</title>
<para>
- Although you can <emphasis>force</emphasis> <command>rpm</command> to install a package that has an unresolved dependency (using the <option>--nodeps</option> option), this is <emphasis>not</emphasis> recommended and will usually result in the installed software failing to run. Installing packages with <option>--nodeps</option> can cause applications to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about missing dependencies. The <application>Yum</application> package manager performs automatic dependency resolution and fetches dependencies from on-line repositories.
+ Although you can <emphasis>force</emphasis> <command>rpm</command> to install a package that has an unresolved dependency (using the <option>--nodeps</option> option), this is <emphasis>not</emphasis> recommended and will usually result in the installed software failing to run. Installing packages with <option>--nodeps</option> can cause applications to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about missing dependencies. The <application>DNF</application> package manager performs automatic dependency resolution and fetches dependencies from on-line repositories.
</para>
</warning>
</section>
@@ -601,7 +601,7 @@ S.5....T. c /etc/abrt/abrt.conf
<primary>packages</primary>
<secondary>initial RPM repositories</secondary>
</indexterm>
- Official <application>RPM</application> repositories provided with the <application>Yum</application> package manager. See <xref linkend="ch-yum"/> for details on how to use the official &MAJOROS; package repositories.
+ Official <application>RPM</application> repositories provided with the <application>DNF</application> package manager. See <xref linkend="ch-DNF"/> for details on how to use the official &MAJOROS; package repositories.
</para>
</listitem>
@@ -642,7 +642,7 @@ S.5....T. c /etc/abrt/abrt.conf
</para>
<synopsis><command>rpmkeys -K <replaceable>package.rpm</replaceable></command></synopsis>
<para>
- Note that the <application>Yum</application> package manager performs automatic checking of <application>GPG</application> signatures during installations and upgrades.
+ Note that the <application>DNF</application> package manager performs automatic checking of <application>GPG</application> signatures during installations and upgrades.
</para>
<para>
<application>GPG</application> is installed by default, as well as a set of Red Hat keys for verifying packages. To import additional keys for use with <application>RPM</application>, see <xref linkend="s2-keys-importing"/>.
@@ -822,7 +822,7 @@ S.5....T. c /etc/abrt/abrt.conf
</indexterm>
<listitem>
<para>
- <xref linkend="ch-yum" /> describes how to use the <application>Yum</application> package manager to search, install, update, and uninstall packages on the command line.
+ <xref linkend="ch-DNF" /> describes how to use the <application>DNF</application> package manager to search, install, update, and uninstall packages on the command line.
</para>
</listitem>
</itemizedlist>
9 years
[system-administrators-guide] Change include directives to DNF
by stephenw
commit 21e65a3fdf5975213ef09cf2a0c499924228d243
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Fri Apr 17 17:08:01 2015 +0200
Change include directives to DNF
en-US/System_Administrators_Guide.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml
index c71fffa..b436cde 100644
--- a/en-US/System_Administrators_Guide.xml
+++ b/en-US/System_Administrators_Guide.xml
@@ -24,10 +24,10 @@
<title>Package Management</title>
<partintro>
<para>
- All software on a &MAJOROS; system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on &MAJOROS; using <application>Yum</application>.
+ All software on a &MAJOROS; system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on &MAJOROS; using <application>DNF</application>.
</para>
</partintro>
- <xi:include href="Yum.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="DNF.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<part id="part-Infrastructure_Services">
<title>Infrastructure Services</title>
9 years