[deployment-guide/comm-rel: 27/35] Merge branch 'master' into comm

dsilas dsilas at fedoraproject.org
Wed Jun 9 12:37:02 UTC 2010


commit 7dafe62eeee94cf96575399b2616be0791fb32a9
Merge: d409be8... e944a3e...
Author: Douglas Silas <dhensley at redhat.com>
Date:   Wed Jun 9 02:00:52 2010 +0200

    Merge branch 'master' into comm
    
    Conflicts:
    	en-US/Deployment_Guide.ent
    	en-US/RPM.xml

 en-US/Feedback.xml |    2 +-
 en-US/RPM.xml      |  148 +++++++++++++++++++++++++--------------------------
 en-US/Yum.xml      |    4 +-
 3 files changed, 76 insertions(+), 78 deletions(-)
---
diff --cc en-US/RPM.xml
index 970c31d,8c9fe0b..6b55c42
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@@ -118,36 -128,55 +123,55 @@@
          <primary>packages</primary>
          <secondary>installing</secondary>
        </indexterm>
-       <para>RPM packages typically have file names like <filename>tree-1.5.2.2-4.&PKGOS;.x86_64.rpm</filename>. The file name includes the package name (<filename>tree</filename>), version (<filename>1.5.2.2</filename>), release (<filename>4</filename>), operating system major version (<filename>&PKGOS;</filename>) and CPU architecture (<filename>x86_64</filename>). Assuming the <filename>tree-1.5.2.2-4.&PKGOS;.x86_64.rpm</filename> package is in the current directory, log in as root and type the following command at a shell prompt to install it:</para>
+       <indexterm
+         significance="normal">
+         <primary>packages</primary>
+         <secondary>upgrading</secondary>
+       </indexterm>
+       <para>RPM packages typically have file names like <filename>tree-1.5.3-2.&PKGOS;.x86_64.rpm</filename>. The file name includes the package name (<filename>tree</filename>), version (<filename>1.5.3</filename>), release (<filename>2</filename>), operating system major version (<filename>&PKGOS;</filename>) and CPU architecture (<filename>x86_64</filename>).</para>
+       <para>You can use <command>rpm</command>'s <option>-U</option> option to:</para>
+       <itemizedlist>
+         <listitem>
+           <para>upgrade an existing but older package on the system to a newer version, or</para>
+         </listitem>
+         <listitem>
+           <para>install the package even if an older version is not already installed.</para>
+         </listitem>
+       </itemizedlist>
+       <para>That is, <command>rpm -U <replaceable>&lt;rpm_file&gt;</replaceable>
+         </command> is able to perform the function of either <emphasis>upgrading</emphasis> or <emphasis>installing</emphasis> as is appropriate for the package.</para>
+       <para>Assuming the <filename>tree-1.5.3-2.&PKGOS;.x86_64.rpm</filename> package is in the current directory, log in as root and type the following command at a shell prompt to either upgrade or install the <package>tree</package> package as determined by <command>rpm</command>:</para>
  			<!-- RHEL5:   BZ#419161			  -->
        <screen>
- <command>rpm -ivh tree-1.5.2.2-4.&PKGOS;.x86_64.rpm</command>
-       </screen>
-       <para>The <option>-i</option> option tells <command>rpm</command> to install the package, and the <option>-v</option> and <option>-h</option> options (which are combined with <option>-i</option>) cause <application>rpm</application> to print more verbose output and display a progress meter using hash marks.</para>
-       <para>Alternatively, you can use the <option>-U</option> option, which <firstterm>upgrades</firstterm> the package if an older version is already installed, or simply installs it if not:</para>
-       <screen>
- <command>rpm -Uvh tree-1.5.2.2-4.&PKGOS;.x86_64.rpm</command>
+ <command>rpm -Uvh tree-1.5.3-2.&PKGOS;.x86_64.rpm</command>
        </screen>
-       <para>If the installation is successful, the following output is displayed:</para>
+       <note
+         id="note-Use_-Uvh_for_nicely-formatted_RPM_installs">
+         <title>Use -Uvh for nicely-formatted RPM installs</title>
+         <para>The <option>-v</option> and <option>-h</option> options (which are combined with <option>-U</option>) cause <application>rpm</application> to print more verbose output and display a progress meter using hash marks.</para>
+       </note>
+       <para>If the upgrade/installation is successful, the following output is displayed:</para>
        <screen>Preparing...                ########################################### [100%]
     1:tree                   ########################################### [100%]</screen>
-       <para>As you can see, RPM prints out the name of the package and then prints a succession of hash marks as a progress meter while the package is installed.</para>
+       <warning
+         id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages">
+         <title>Always use the -i (install) option to install new kernel packages!</title>
+         <para>
+           <command>rpm</command> provides two different options for installing packages: the aforementioned <option>-U</option> option (which historically stands for <emphasis>upgrade</emphasis>), and the <option>-i</option> option, historically standing for <emphasis>install</emphasis>. Because the <option>-U</option> option subsumes both install and upgrade functions, we recommend to use <command>rpm -Uvh</command> with all packages <emphasis>except <package>kernel</package> packages</emphasis>.</para>
+         <para>You should always use the <option>-i</option> option to simply <emphasis>install</emphasis> a new kernel package instead of upgrading it. This is because using the <option>-U</option> option to upgrade a kernel package removes the previous (older) kernel package, which could render the system unable to boot if there is a problem with the new kernel. Therefore, use <command>rpm -i</command> command to install a new kernel <emphasis>without replacing any older <package>kernel</package> packages</emphasis>. For more information on installing <package>kernel</package> packages, refer to <xref
+             linkend="ch-Manually_Upgrading_the_Kernel"/>.</para>
+       </warning>
        <para>The signature of a package is checked automatically when installing or upgrading a package. The signature confirms that the package was signed by an authorized party. For example, if the verification of the signature fails, an error message such as the following is displayed:</para>
 -      <screen>error: tree-1.5.3-2.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
 +      <screen>error: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
  d22e77f2</screen>
  <!-- TBD6: clarify: what is a "new, header-only, signature"? -->
        <para>If it is a new, header-only, signature, an error message such as the following is displayed:</para>
 -      <screen>error: tree-1.5.3-2.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
 +      <screen>error: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
  key ID d22e77f2</screen>
        <para>If you do not have the appropriate key installed to verify the signature, the message contains the word <computeroutput>NOKEY</computeroutput>:</para>
 -      <screen>warning: tree-1.5.3-2.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</screen>
 +      <screen>warning: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</screen>
        <para>Refer to <xref
            linkend="s1-check-rpm-sig"/> for more information on checking a package's signature.</para>
-       <warning>
-         <title>Warning</title>
-         <para>If you are installing a kernel package, you should always use the <command>rpm -ivh</command> command (simple install) instead of <command>rpm -Uvh</command>. The reason for this is that <emphasis>install</emphasis> (<option>-i</option>) and <emphasis>upgrade</emphasis> (<option>-U</option>) take on specific meanings when installing kernel packages. Refer to <xref
-             linkend="ch-Manually_Upgrading_the_Kernel"/> for details.</para>
-       </warning>
        <section
          id="s3-rpm-errors">
          <title>Package Already Installed</title>
@@@ -575,13 -583,13 +578,9 @@@ ghostscript-8.70-1.&PKGOS;.x86_64</scre
          </screen>
          <para>The output would be similar to the following:</para>
          <screen>Name        : crontabs                     Relocations: (not relocatable)
- Version     : 1.10                              Vendor: Fedora Project
- Release     : 31.&PKGOS;                       Build Date: Sat 25 Jul 2009 06:37:57 AM CEST
- Install Date: (not installed)               Build Host: x86-6.fedora.phx.redhat.com
- Group       : System Environment/Base       Source RPM: crontabs-1.10-31.&PKGOS;.src.rpm
 -Version     : 1.10                              Vendor: Red Hat, Inc.
 -Release     : 32.1.&PKGOS;                      Build Date: Thu 03 Dec 2009 02:17:44 AM CET
 -Install Date: (not installed)               Build Host: js20-bc1-11.build.redhat.com
 -Group       : System Environment/Base       Source RPM: crontabs-1.10-32.1.&PKGOS;.src.rpm
  Size        : 2486                             License: Public Domain and GPLv2
 -Signature   : RSA/8, Wed 24 Feb 2010 08:46:13 PM CET, Key ID 938a80caf21541eb
 -Packager    : Red Hat, Inc. &lt;http://bugzilla.redhat.com/bugzilla&gt;
 +Signature   : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba
 +Packager    : Fedora Project
  Summary     : Root crontab files used to schedule the execution of programs
  Description :
  The crontabs package contains root crontab files and directories.


More information about the docs-commits mailing list