From ef0b91a5129473b9e82f8f6e86cf387e61d48747 Mon Sep 17 00:00:00 2001 From: Douglas Silas Date: May 13 2010 15:34:23 +0000 Subject: Merge branch 'master' into fedora --- diff --git a/en-US/Deployment_Guide.ent b/en-US/Deployment_Guide.ent index 77dd77d..eec34ff 100644 --- a/en-US/Deployment_Guide.ent +++ b/en-US/Deployment_Guide.ent @@ -3,6 +3,7 @@ + diff --git a/en-US/RPM.xml b/en-US/RPM.xml index 339facb..2d2f4fe 100644 --- a/en-US/RPM.xml +++ b/en-US/RPM.xml @@ -124,29 +124,29 @@ packages installing - RPM packages typically have file names like tree-1.5.2.2-4.fc12.x86_64.rpm. The file name includes the package name (tree), version (1.5.2.2), release (4), operating system major version (fc12) and CPU architecture (x86_64). Assuming the tree-1.5.2.2-4.fc12.x86_64.rpm package is in the current directory, log in as root and type the following command at a shell prompt to install it: + RPM packages typically have file names like tree-1.5.2.2-4.&PKGOS;.x86_64.rpm. The file name includes the package name (tree), version (1.5.2.2), release (4), operating system major version (&PKGOS;) and CPU architecture (x86_64). Assuming the tree-1.5.2.2-4.&PKGOS;.x86_64.rpm package is in the current directory, log in as root and type the following command at a shell prompt to install it: -rpm -ivh tree-1.5.2.2-4.fc12.x86_64.rpm +rpm -ivh tree-1.5.2.2-4.&PKGOS;.x86_64.rpm The option tells rpm to install the package, and the and options (which are combined with ) cause rpm to print more verbose output and display a progress meter using hash marks. Alternatively, you can use the option, which upgrades the package if an older version is already installed, or simply installs it if not: -rpm -Uvh tree-1.5.2.2-4.fc12.x86_64.rpm +rpm -Uvh tree-1.5.2.2-4.&PKGOS;.x86_64.rpm If the installation is successful, the following output is displayed: Preparing... ########################################### [100%] 1:tree ########################################### [100%] 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. 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: - error: tree-1.5.2.2-4.fc12.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID + error: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID d22e77f2 If it is a new, header-only, signature, an error message such as the following is displayed: - error: tree-1.5.2.2-4.fc12.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, + error: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID d22e77f2 If you do not have the appropriate key installed to verify the signature, the message contains the word NOKEY: - warning: tree-1.5.2.2-4.fc12.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba + warning: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba Refer to for more information on checking a package's signature. @@ -159,10 +159,10 @@ key ID d22e77f2 Package Already Installed If a package of the same name and version is already installed, the following output is displayed: Preparing... ########################################### [100%] - package tree-1.5.2.2-4.fc12.x86_64 is already installed + package tree-1.5.2.2-4.&PKGOS;.x86_64 is already installed However, if you want to install the package anyway, you can use the --replacepkgs option, which tells RPM to ignore the error: -rpm -ivh --replacepkgs tree-1.5.2.2-4.fc12.x86_64.rpm +rpm -ivh --replacepkgs tree-1.5.2.2-4.&PKGOS;.x86_64.rpm This option is helpful if files installed from the RPM were deleted or if you want the original configuration files from the RPM to be installed. @@ -177,11 +177,11 @@ key ID d22e77f2 If you attempt to install a package that contains a file which has already been installed by another package, the following is displayed: Preparing... ################################################## - file /usr/bin/foobar from install of foo-1.0-1.fc12 conflicts -with file from package bar-3.1.1.fc12 + file /usr/bin/foobar from install of foo-1.0-1.&PKGOS; conflicts +with file from package bar-3.1.1.&PKGOS; To make RPM ignore this error, use the --replacefiles option: -rpm -ivh --replacefiles foo-1.0-1.fc12.x86_64.rpm +rpm -ivh --replacefiles foo-1.0-1.&PKGOS;.x86_64.rpm
error: Failed dependencies: - bar.so.3()(64bit) is needed by foo-1.0-1.fc12.x86_64 + bar.so.3()(64bit) is needed by foo-1.0-1.&PKGOS;.x86_64 Suggested resolutions: - bar-3.1.1.fc12.x86_64.rpm + bar-3.1.1.&PKGOS;.x86_64.rpm If you are installing a package from the &MAJOROS; installation media, such as from a CD-ROM or DVD, it usually suggests the package or packages needed to resolve the dependency. Find the suggested package(s) on the &MAJOROS; installation media or on one of the active &MAJOROS; mirrors () and add it to the command: -rpm -ivh foo-1.0-1.fc12.x86_64.rpm    bar-3.1.1.fc12.x86_64.rpm + rpm -ivh foo-1.0-1.&PKGOS;.x86_64.rpm    bar-3.1.1.&PKGOS;.x86_64.rpm If installation of both packages is successful, output similar to the following is displayed: Preparing... ########################################### [100%] @@ -218,7 +218,7 @@ with file from package bar-3.1.1.fc12 rpm -q --whatprovides "bar.so.3" If the package that contains bar.so.3 is in the RPM database, the name of the package is displayed: - bar-3.1.1.fc12.i586.rpm + bar-3.1.1.&PKGOS;.i586.rpm Warning: Forcing Package Installation @@ -245,21 +245,21 @@ with file from package bar-3.1.1.fc12 Note Notice that we used the package name - foo, not the name of the original package file, foo-1.0-1.fc12.x86_64. If you attempt to uninstall a package using the rpm -e command and the original full file name, you will receive a package name error. + foo, not the name of the original package file, foo-1.0-1.&PKGOS;.x86_64. If you attempt to uninstall a package using the rpm -e command and the original full file name, you will receive a package name error. You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example: rpm -e ghostscript error: Failed dependencies: - libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.fc12.x86_64 - libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc12.x86_64 - libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc12.x86_64 - ghostscript is needed by (installed) printer-filters-1.1-4.fc12.noarch + libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.&PKGOS;.x86_64 + libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.&PKGOS;.x86_64 + libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.&PKGOS;.x86_64 + ghostscript is needed by (installed) printer-filters-1.1-4.&PKGOS;.noarch Similar to how we searched for a shared object library (i.e. a <library_name>.so.<number> file) in , we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name): ~]# rpm -q --whatprovides "libgs.so.8()(64bit)" -ghostscript-8.70-1.fc12.x86_64 +ghostscript-8.70-1.&PKGOS;.x86_64 Warning: Forcing Package Installation @@ -280,9 +280,9 @@ ghostscript-8.70-1.fc12.x86_64 packages upgrading - Upgrading a package (using the option) is similar to installing one (the option). If we have the RPM named tree-1.5.3.0-1.fc12.x86_64.rpm in our current directory, and tree-1.5.2.2-4.fc12.x86_64.rpm is already installed on our system (rpm -qi will tell us which version of the tree package we have installed on our system, if any), then the following command will upgrade tree to the newer version: + Upgrading a package (using the option) is similar to installing one (the option). If we have the RPM named tree-1.5.3.0-1.&PKGOS;.x86_64.rpm in our current directory, and tree-1.5.2.2-4.&PKGOS;.x86_64.rpm is already installed on our system (rpm -qi will tell us which version of the tree package we have installed on our system, if any), then the following command will upgrade tree to the newer version: -rpm -Uvh tree-1.5.3.0-1.fc12.x86_64.rpm +rpm -Uvh tree-1.5.3.0-1.&PKGOS;.x86_64.rpm As part of upgrading a package, RPM automatically uninstalls any old versions of the foo package. Note that will also install a package even when there are no previous versions of the package installed. @@ -305,10 +305,10 @@ ghostscript-8.70-1.fc12.x86_64 This message means that changes you made to the configuration file may not be forward-compatible with the new configuration file in the package, so RPM saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible, to ensure that your system continues to function properly. Alternatively, RPM may save the package's new configuration file as, for example, foo.conf.rpmnew, and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one with a diff program. If you attempt to upgrade to a package with an older version number (that is, if a higher version of the package is already installed), the output is similar to the following: - package foo-2.0-1.fc12.x86_64.rpm (which is newer than foo-1.0-1) is already installed + package foo-2.0-1.&PKGOS;.x86_64.rpm (which is newer than foo-1.0-1) is already installed To force RPM to upgrade anyway, use the --oldpackage option: -rpm -Uvh --oldpackage foo-1.0-1.fc12.x86_64.rpm +rpm -Uvh --oldpackage foo-1.0-1.&PKGOS;.x86_64.rpm
Freshening is similar to upgrading, except that only existent packages are upgraded. Type the following command at a shell prompt: -rpm -Fvh foo-2.0-1.fc12.x86_64.rpm +rpm -Fvh foo-2.0-1.&PKGOS;.x86_64.rpm RPM's freshen option checks the versions of the packages specified on the command line against the versions of packages that have already been installed on your system. When a newer version of an already-installed package is processed by RPM's freshen option, it is upgraded to the newer version. However, RPM's freshen option does not install a package if no previously-installed package of the same name exists. This differs from RPM's upgrade option, as an upgrade does install packages whether or not an older version of the package was already installed. Freshening works for single packages or package groups. If you have just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system, freshening does the job. Thus, you do not have to delete any unwanted packages from the group that you downloaded before using RPM. @@ -357,7 +357,7 @@ ghostscript-8.70-1.fc12.x86_64 The RPM database stores information about all RPM packages installed in your system. It is stored in the directory /var/lib/rpm/, and is used to query what packages are installed, what versions each package is, and to calculate any changes to any files in the package since installation, among other use cases. To query this database, use the -q option. The rpm -q package name command displays the package name, version, and release number of the installed package <package_name>. For example, using rpm -q tree to query installed package tree might generate the following output: - tree-1.5.2.2-4.fc12.x86_64 + tree-1.5.2.2-4.&PKGOS;.x86_64 You can also use the following Package Selection Options (which is a subheading in the RPM man page: see man rpm for details) to further refine or qualify your query: @@ -438,7 +438,7 @@ ghostscript-8.70-1.fc12.x86_64 To verify an installed package against an RPM package file: -rpm -Vp tree-1.5.2.2-4.fc12.x86_64.rpm +rpm -Vp tree-1.5.2.2-4.&PKGOS;.x86_64.rpm This command can be useful if you suspect that your RPM database is corrupt. @@ -539,7 +539,7 @@ ghostscript-8.70-1.fc12.x86_64 rpm -qf /usr/bin/ghostscript The output would look like the following: - ghostscript-8.70-1.fc12.x86_64 + ghostscript-8.70-1.&PKGOS;.x86_64 We can combine the above two examples in the following scenario. Say you are having problems with /usr/bin/paste. You would like to verify the package that owns that program, but you do not know which package owns paste. Enter the following command, @@ -604,14 +604,14 @@ ghostscript-8.70-1.fc12.x86_64 querying uninstalled -rpm -qip crontabs-1.10-31.fc12.noarch.rpm +rpm -qip crontabs-1.10-31.&PKGOS;.noarch.rpm The output would be similar to the following: Name : crontabs Relocations: (not relocatable) Version : 1.10 Vendor: Fedora Project -Release : 31.fc12 Build Date: Sat 25 Jul 2009 06:37:57 AM CEST +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.fc12.src.rpm +Group : System Environment/Base Source RPM: crontabs-1.10-31.&PKGOS;.src.rpm Size : 2486 License: Public Domain and GPLv2 Signature : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba Packager : Fedora Project @@ -639,7 +639,7 @@ your system. obtaining list of files -rpm -qlp crontabs-1.10-31.fc12.noarch.rpm +rpm -qlp crontabs-1.10-31.&PKGOS;.noarch.rpm The output is similar to the following: /etc/cron.daily