head 1.2; access; symbols RPM_3_0_2:1.1.1.11 RPM_3_0_1:1.1.1.11 RPM_3_0:1.1.1.10 RPM_2_5_6:1.1.1.9 RPM_2_5:1.1.1.8 RPM_2_4_12:1.1.1.7 RPM_2_4:1.1.1.6 RPM_2_3_11:1.1.1.6 RPM_2_3:1.1.1.5 RPM_2_2_11:1.1.1.5 RPM_2_2:1.1.1.4 RPM_2_1_2:1.1.1.3 RPM_2_1:1.1.1.3 RPM_2_0_11:1.1.1.2 RPM_2_0:1.1.1.1 RPM:1.1.1; locks; strict; comment @.\" @; 1.2 date 2003.08.24.12.02.22; author rse; state dead; branches; next 1.1; 1.1 date 96.03.05.16.16.58; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 96.03.05.16.16.58; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 96.06.04.20.26.44; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 96.07.10.20.51.19; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 96.07.16.16.54.52; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 96.12.20.22.51.04; author rse; state Exp; branches; next 1.1.1.6; 1.1.1.6 date 97.04.23.17.08.58; author rse; state Exp; branches; next 1.1.1.7; 1.1.1.7 date 98.01.08.15.53.22; author rse; state Exp; branches; next 1.1.1.8; 1.1.1.8 date 98.05.10.18.40.30; author rse; state Exp; branches; next 1.1.1.9; 1.1.1.9 date 98.08.25.19.06.11; author rse; state Exp; branches; next 1.1.1.10; 1.1.1.10 date 99.04.17.08.05.25; author rse; state Exp; branches; next 1.1.1.11; 1.1.1.11 date 99.05.15.14.44.04; author rse; state Exp; branches; next ; desc @@ 1.2 log @Resolve: RPM 3.0.2 -> RPM 3.0.3 @ text @.\" rpm - Red Hat Package Manager .TH rpm 8 "25 February 1996" "Red Hat Software" "Red Hat Linux" .SH NAME rpm \- Red Hat Package Manager .SH SYNOPSIS \fBrpm\fP [options] .SH DESCRIPTION \fBrpm\fP is a powerful \fIpackage manager\fP, which can be used to build, install, query, verify, update, and uninstall individual software packages. A \fIpackage\fP consists of an archive of files, and package information, including name, version, and description. There are five basic modes of operation, and each takes a different set of options. They are \fIbuild\fP, \fIinstall\fP, \fIquery\fP, \fIverify\fP, \FIsignature check\fP, and \fIuninstall\fP. .I "\fBrpm \-i [install\-options] +\fP" .br .I "\fBrpm \-q [query\-options]\fP" .br .I "\fBrpm \-V|\-y|\-\-verify [verify\-options]\fP" .br .I "\fBrpm \-\-checksig +\fP" .br .I "\fBrpm \-e +\fP" .br .I "\fBrpm \-b\fIO\fB [build\-options] +\fP" .SH INSTALL OPTIONS .IP "\fB\-\-force\fP" Same as using both \-\-replacepkgs, \-\-replacefiles, and \-\-oldpackage. .IP "\fB\-h, \-\-hash\fP" Print 50 hash marks as the package archive is unpacked. Use with \fB\-v\fP for a nice display. .IP "\fB\-\-oldpackage\fP" Allow an upgrade to replace a newer package with an older one. .IP "\fB\-\-percent\fP" Print percentages as files are unpacked from the package archive. This is intended to make RPM easy to run from other tools. .IP "\fB\-\-replacefiles\fP" Install the packages even if they replace files from other, already installed, packages. .IP "\fB\-\-replacepkgs\fP" Install the packages even if some of them are already installed on this system. .IP "\fB\-\-root \fI\fP" Do the installation on the system rooted at \fI\fP. Note that this means the database will be updated under \fI\fP and any \fIpre\fP or \fIpost\fP scripts are run after a chroot() to \fI\fP. .IP "\fB\-S, \-\-search\fP" Search the locations listed in /etc/rpmrc for the rpm. .IP "\fB\-\-test\fP" Do not install the package, simply check for and report potential conflicts. .IP "\fB\-U, \-\-upgrade\fP" Upgrade the package currently installed to the version in the new RPM. This is the same as install, except all other version of the package are removed from the system. .SH UNINSTALL OPTIONS .IP "\fB\-\-test\fP" Don't really uninstall anything, just go through the motions. This is designed primarily for testing and should normally be used with the \fB\-vv\fP option. .SH BUILD OPTIONS The general form of a rpm build command is .PP \fBrpm \-b\fIO\fB [build\-options] +\fP .PP where \fB\-b\fIO\fP specifies the stages of building and packaging to be done and is one of: .IP "\fB\-bp\fP" Executes the "%prep" stage from the spec file. Normally this involves unpacking the sources and applying any patches. .IP "\fB\-bl\fP" Do a "list check". The "%files" section from the spec file is macro expanded, and checks are made to insure the files exist. .IP "\fB\-bc\fP" Do the "%build" stage from the spec file (after doing the prep stage). This generally involves the equivalent of a "make". .IP "\fB\-bi\fP" Do the "%install" stage from the spec file (after doing the prep and build stages). This generally involves the equivalent of a "make install". .IP "\fB\-bb\fP" Build a binary package (after doing the prep, build, and install stages). .IP "\fB\-ba\fP" Build binary and source packages (after doing the prep, build, and install stages). .PP The following options may also be used: .IP "\fB\-\-short\-circuit\fP" Skip straight to specified stage (ie, skip all stages leading up to the specified stage). Only valid for \fB\-bc\fP and \fB\-bi\fP. .IP "\fB\-\-clean\fP" Remove the build tree after the packages are made. .IP "\fB\-\-test\fP" Do not execute any build stages. Implies \fB\-\-keep\-temps\fP. Useful for testing out spec files. .IP "\fB\-\-sign\fP" Embed a PGP signature in the package. This signature can be used to verify the integrity and the origin of the package. See the section on PGP SIGNATURES for /etc/rpmrc details. .SH QUERY OPTIONS There are two sets of options for querying: package selection, and information selection. Package selection options: .br .IP "\fB\fI\fP" Query pacakge named \fB\fI\fP. .IP "\fB\-a\fP" Query all packages .IP "\fB\-f \fI\fP" Query package owning \fI\fP. .IP "\fB\-F\fP" Like \fB\-f\fP but read file names from stdin. .IP "\fB\-p \fI\fP" Query an (uninstalled) package \fI\fP. .IP "\fB\-P\fP" Like \fB\-p\fP but read package file names from stdin. .br Information selection options: .br .IP "\fB\-i\fP" Display package information, including name, version, and description. .IP "\fB\-l\fP" List files in package. .IP "\fB\-s\fP" Display \fIstates\fP of file in package (implies \fB\-l\fP). The state of each package is either \fInormal\fP or \fIoverwritten\fP. .IP "\fB\-d\fP" List only documentation files (implies \fB\-l\fP). .IP "\fB\-c\fP" List only configuration files (implies \fB\-l\fP). .SH VERIFY OPTIONS Verifying a package compares information about the installed files in the package with information about the files taken from the original package and stored in the rpm database. Among other things, verifying compares the size, MD5 sum, permissions, type, owner and group of each file. Any discrepencies are displayed. The package specification options are the same as for package querying. The format of the output is a string of 8 characters, an optional "\fBc\fP" denoting a configuration file, and then the file name. Each of the 8 characters denotes the result of a comparison of one aspect of the file to that aspect as recorded in the RPM database. A single "\fB.\fP" (period) means the test passed. The following characters denote failure of certain tests: .IP "\fB5\fP" MD5 sum .IP "\fBS\fP" File size .IP "\fBL\fP" Symlink .IP "\fBT\fP" Mtime .IP "\fBD\fP" Device .IP "\fBU\fP" User .IP "\fBG\fP" Group .IP "\fBM\fP" Mode (includes permissions and file type) .SH SIGNATURE CHECKING This checks the PGP signature built into a package to ensure the integrity and the origin of the package. PGP configuration information is read from /etc/rpmrc. See the section on PGP SIGNATURES for details. .SH REBUILD OPTION There is another way to invoke rpm: .I "\fBrpm \-\-rebuild +\fP" When invoked this way, rpm installs the named source package, and builds a binary package from it as if it were invoked as: .SH WHERE OPTION There is one more option that can be used to invoke rpm: .IP "\fB\-w, \-\-where\fP" This causes rpm to search the locations listed in /etc/rpmrc for any rpm matching those listed as arguments on the command line. .SH GENERAL OPTIONS These options can be used in all the different modes. .IP "\fB\-vv\fP" Print lots of ugly debugging information. .IP "\fB\-\-keep\-temps\fP" Do not remove temporary files (/tmp/rpm\-*). Primarily only useful for debugging rpm. .IP "\fB\-\-quiet\fP" Print as little as possible \- normally only error messages will be displayed. .IP "\fB\-\-help\fP" Print a longer usage message then normal. .IP "\fB\-\-version\fP" Print a single line containing the version number of rpm being used. .IP "\fB\-\-root \fP" Use the directory given as top level directory for all operations. .SH PGP SIGNATURES In order to use the signature feature RPM must be able to run PGP (it must be installed and in your path), and it must be able to find a public key ring with RPM public keys in it. By default, RPM looks in /usr/lib/rpm for both pubring.pgp and secring.pgp (which is used during package builds). If your key rings are not located there you must set the following on your /etc/rpmrc .IP "\fBpgp_path\fP" Replacement path for /usr/lib/rpm. Must contain your key rings. .IP "\fBpgp_pubring\fP" The full path to your public key ring. .IP "\fBpgp_secring\fP" The full path to your public key ring. .PP The bare minimum you need to do to get PGP singature checking working is install PGP and run the following: .nf mkdir -p /usr/lib/rpm cd /usr/lib/rpm cp /mnt/crom/RPM-PGP-KEY . touch config.txt pgp -ka RPM-PGP-KEY pubring.pgp .fi You should then be able to check the signatures of packages produced by Red Hat Software using pgp \-K. If you want to be able to sign packages you create yourself, you also need to create your own public and secret key pair (see the PGP manual). In addition to the above /etc/rpmrc entries, you should add the following: .IP "\fBsignature\fP" The signature type. Right now only pgp is supported. .IP "\fBpgp_name\fP" The name of the "user" whose key you wish to use to sign your packages. .PP When building packages you then add \-\-sign to the command line. You will be prompted for your pass phrase, and your package will be built and signed. .SH FILES .nf /etc/rpmrc /var/lib/rpm/packages /var/lib/rpm/pathidx /var/lib/rpm/nameidx /tmp/rpm-* .fi .El .SH SEE ALSO .IR glint (8) , .IR rpm2cpio (8) , .B http://www.redhat.com/RPM-HOWTO .nf .SH AUTHORS .nf Marc Ewing Erik Troan .fi @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 2.0 @ text @@ 1.1.1.2 log @Import: RPM 2.0.11 @ text @d2 1 a2 1 .TH rpm 8 "29 March 1996" "Red Hat Software" "Red Hat Linux" d51 2 a52 8 .IP "\fB\-\-noscripts\fP" Don't execute the preinstall or postinstall scripts. .IP "\fB\-\-excludedocs\fP" Don't install any files which are marked as documentation (which includes man pages and texinfo documents). .IP "\fB\-\-includedocs\fP" Install documentation files. This is only needed if \fIexcludedocs: 1\fP is specified in an rpmrc file. a61 2 .IP "\fB\-\-noscripts\fP" Don't execute the preuninstall or postuninstall scripts. d70 1 a70 1 \fBrpm \-b\fIO\fP [build\-options] +\fP d72 1 a72 1 where \fB\-bO\fP specifies the stages of building and d110 1 a110 25 You may specify the format that the header portion should be printed in. To do this, you use the "\fB\--queryformat\fP" option, followed by the format string. Query formats are modifed versions of the standard \fBprintf(3)\fP formatting. The format is made up of static strings (which may include standard C character escapes for newlines, tabs, and other special characters) and the \fBprintf(3)\fP type formatters. As \fBrpm\fP already knows the type to print, the type specifier must be omitted however, and replaced by the name of the header tag to be printed, which is enclosed by \fB{}\fP characters. The \fBRPMTAG_\fP portion of the tag name may be omitted, and the tag name may be preceded by a \fB-\fP to format the tag as a date if possible. For example, to print only the names of the packages queried, you could use \fB%{NAME}\fP as the format string. To print the packages name and distribution information in two columns, you could use \fB%-30{NAME}%{DISTRIBUTION}\fP. \fBrpm\fP will print a list of all of the tags it knows about when it is invoked with the \fB--querytags\fP argument and nothing else. There are two subsets of options for querying: package selection, and d137 1 a137 1 either \fInormal\fP, \fInot installed\fP, or \fIreplaced\fP. a141 3 .IP "\fB\-\-scripts\fP" List the package specific shell scripts that are used as part of the installation and uninstallation processes, if there are any. d181 1 a181 1 .SH REBUILD AND RECOMPILE OPTIONS d183 1 a183 3 There are two other ways to invoke rpm: .I "\fBrpm \-\-recompile +\fP" d187 2 a188 5 When invoked this way, rpm installs the named source package, and does a prep, compile and install. In addition, \-\-rebuild builds a new binary package. .SH SIGNING AN EXISTING RPM d190 1 a190 1 .I "\fBrpm \-\-resign +\fP" d192 1 a192 2 This option generates and inserts new signatures for the listed packages. Any existing signatures are removed. d194 3 d202 3 a211 2 .IP "\fB\-\-rcfile \fP" Use \fB\fP instead of \fB/etc/rpmrc\fP and \fB$HOME/.rpmrc\fP. d229 1 a229 1 The full path to your secret key ring. d243 1 a243 1 by Red Hat Software using rpm \-K. a262 1 ~/.rpmrc d272 1 a272 1 .B http://www.redhat.com/redhat/support/docs/HOWTO/RPM-HOWTO @ 1.1.1.3 log @Import: RPM 2.1 @ text @d13 1 a13 1 There are six basic modes of operation, and each takes a different d15 1 a15 1 \fIverify\fP, \fIsignature check\fP, and \fIuninstall\fP. a58 2 .IP "\fB\-\-nodeps\fP" Don't check dependencies before installing the packages. a69 2 .IP "\fB\-\-nodeps\fP" Don't check dependencies before uninstalling the packages. d71 2 a72 1 Don't really uninstall anything, just go through the motions. d80 1 a80 1 where \fB\-b\fIO\fR specifies the stages of building and d106 1 a106 1 to the specified stage). Only valid with \fB\-bc\fP and \fB\-bi\fP. d110 1 a110 1 Do not execute any build stages. d119 2 a120 2 You may specify the format that package information should be printed in. To do this, you use the \fB\-\-queryformat\fP option, followed by d126 1 a126 1 characters) and \fBprintf(3)\fP type formatters. As \fBrpm\fP d129 1 a129 1 be printed, enclosed by \fB{}\fP characters. The d131 1 a131 1 tag name may be preceded by a \fB\-\fP to format the tag as d137 1 a137 1 \fB%\-30{NAME}%{DISTRIBUTION}\fP. d140 1 a140 1 it is invoked with the \fB\-\-querytags\fP argument. d148 1 a148 1 Query package named \fB\fI\fP. a150 4 .IP "\fB\-whatrequires \fI\fP" Query all packages that requires \fI\fP for proper functioning. .IP "\fB\-whatprovides \fI\fP" Query all packages that provide the \fI\fP capability. d159 1 a159 2 .P d163 1 a163 6 Display package information, including name, version, and description. This uses the \fB\-\-queryformat\fP if one was specified. .IP "\fB\-R\fP" List packages this one depends on (same as \fB\-\-requires\fP). .IP "\fB\-\-provides\fP" List capabilities this package provides. d167 2 a168 2 Display the \fIstates\fP of files in the package (implies \fB\-l\fP). The state of each file is a176 4 .IP "\fB\-\-dump\fP" Dump file information as follows: path size mtime md5sum mode owner group isconfig isdoc rdev symlink. This must be used with at least one of \fB\-l\fP, \fB\-c\fP, \fB\-d\fP. d186 1 a186 1 The format of the output is a string of 8 characters, a possible "\fBc\fP" d188 4 a191 4 characters denotes the result of a comparison of one attribute of the file to the value of that attribute recorded in the RPM database. A single "\fB.\fP" (period) means the test passed. The following characters denote failure of certain tests: d225 2 a226 4 a prep, compile and install. In addition, \fB\-\-rebuild\fP builds a new binary package. When the build has completed, the build directory is removed (as in \fB\-\-clean\fP) and the the sources and spec file for the package are removed. d257 3 a259 3 RPM uses the PGP defaults to find the keyrings (honoring PGPPATH). If your key rings are not located where PGP expects them to be, you must set the following in your /etc/rpmrc d263 4 d268 13 d304 1 a304 1 /tmp/rpm* d310 1 a310 1 .B http://www.redhat.com/rpm @ 1.1.1.4 log @Import: RPM 2.2 @ text @d2 1 a2 1 .TH rpm 8 "15 July 1996" "Red Hat Software" "Red Hat Linux" d14 2 a15 2 set of options. They are \fIInstall\fP, \fIQuery\fP, \fIVerify\fP, \fISignature check\fP, \fIUninstall\fP, \fIBuild\fP. d17 1 a17 1 Install mode: d19 1 a19 1 .I "\fB rpm \-i [install\-options] +\fP" d21 1 a21 1 Query mode: d23 1 a23 1 .I "\fB rpm \-q [query\-options]\fP" d25 1 a25 14 Verify mode: .br .I "\fB rpm \-V|\-y|\-\-verify [verify\-options]\fP" .br Signature Check mode: .br .I "\fB rpm \-\-checksig +\fP" .br Uninstall mode: .br .I "\fB rpm \-e +\fP" Build mode: .br .I "\fB rpm \-b\fIO\fB [build\-options] +\fP" d27 1 a27 19 .SH GENERAL OPTIONS These options can be used in all the different modes. .IP "\fB\-vv\fP" Print lots of ugly debugging information. .IP "\fB\-\-keep\-temps\fP" Do not remove temporary files (/tmp/rpm\-*). Primarily only useful for debugging rpm. .IP "\fB\-\-quiet\fP" Print as little as possible \- normally only error messages will be displayed. .IP "\fB\-\-help\fP" Print a longer usage message then normal. .IP "\fB\-\-version\fP" Print a single line containing the version number of rpm being used. .IP "\fB\-\-rcfile \fP" Use \fB\fP instead of \fB/etc/rpmrc\fP and \fB$HOME/.rpmrc\fP. .IP "\fB\-\-root \fP" Use the directory given as top level directory for all operations. a29 4 The general form of an rpm install command is .PP \fBrpm \-i [install\-options] +\fP .PP d69 16 d86 33 d121 1 a121 4 The general form of an rpm query command is .PP \fBrpm \-q [query\-options]\fP .PP a195 4 The general form of an rpm verify command is .PP \fBrpm \-V|\-y|\-\-verify [verify\-options]\fP .PP a227 4 The general form of an rpm signature check command is .PP \fBrpm \-\-checksig +\fP .PP a232 55 .SH UNINSTALL OPTIONS The general form of an rpm uninstall command is .PP \fB rpm \-e +\fP .PP .IP "\fB\-\-noscripts\fP" Don't execute the preuninstall or postuninstall scripts. .IP "\fB\-\-nodeps\fP" Don't check dependencies before uninstalling the packages. .IP "\fB\-\-test\fP" Don't really uninstall anything, just go through the motions. \fB\-vv\fP option. .SH BUILD OPTIONS The general form of an rpm build command is .PP \fBrpm \-b\fIO\fP [build\-options] +\fP .PP where \fB\-b\fIO\fR specifies the stages of building and packaging to be done and is one of: .IP "\fB\-bp\fP" Executes the "%prep" stage from the spec file. Normally this involves unpacking the sources and applying any patches. .IP "\fB\-bl\fP" Do a "list check". The "%files" section from the spec file is macro expanded, and checks are made to insure the files exist. .IP "\fB\-bc\fP" Do the "%build" stage from the spec file (after doing the prep stage). This generally involves the equivalent of a "make". .IP "\fB\-bi\fP" Do the "%install" stage from the spec file (after doing the prep and build stages). This generally involves the equivalent of a "make install". .IP "\fB\-bb\fP" Build a binary package (after doing the prep, build, and install stages). .IP "\fB\-ba\fP" Build binary and source packages (after doing the prep, build, and install stages). .PP The following options may also be used: .IP "\fB\-\-short\-circuit\fP" Skip straight to specified stage (ie, skip all stages leading up to the specified stage). Only valid with \fB\-bc\fP and \fB\-bi\fP. .IP "\fB\-\-clean\fP" Remove the build tree after the packages are made. .IP "\fB\-\-test\fP" Do not execute any build stages. Useful for testing out spec files. .IP "\fB\-\-sign\fP" Embed a PGP signature in the package. This signature can be used to verify the integrity and the origin of the package. See the section on PGP SIGNATURES for /etc/rpmrc details. d253 17 @ 1.1.1.5 log @Import: RPM 2.2.11 @ text @d13 1 a13 1 There are eight basic modes of operation, and each takes a different d15 1 a15 2 \fIVerify\fP, \fISignature check\fP, \fIUninstall\fP, \fIBuild\fP, \fIRebuild Database\fP, and \fIShow RC\fP. a35 1 .br a64 4 The may be specified as an ftp style URL, in which case the package will be downloaded before being installed. See \fBFTP OPTIONS\fP for information on RPM's built in ftp support. .PP a85 2 .IP "\fB\-\-nodeps\fP" Don't do a dependency check before installing the new package. d152 1 a152 4 Query an (uninstalled) package \fI\fP. The may be specified as an ftp style URL, in which case the package header will be downloaded and queried. See \fBFTP OPTIONS\fP for information on RPM's built in ftp support. a195 4 Files that were not installed from the package, for example documentation files excluded on installation using the "\fB\-\-excludedocs\fP" option, will be silently ignored. a241 2 .IP "\fB\-\-nodeps\fP" Don't check for broken dependencies before removing the package. a274 5 .IP "\fB\-\-timecheck\fP" Set the "timecheck" age (0 to disable). This value can also be set in rpmrc with "timecheck:". The timecheck value expresses, in seconds, the maximum age of a file being packaged. Warnings will be printed for all files beyond the timecheck age. a332 45 .SH REBUILD DATABASE OPTIONS The general form of an rpm rebuild database command is .PP \fBrpm \-\-rebuilddb\fP .PP The only options this mode supports are \fB-\-dbpath\fP and \fB-\-root\fP. .SH SHOWRC Running .PP \fBrpm \-\-showrc\fP .PP shows the values RPM will use for all of the options that may be set in \fIrpmrc\fP files. .SH FTP OPTIONS RPM includes a simple FTP client to simplify installing and querying packages which are available over the internet. Package files for install, upgrade, and query operations may be specified as an ftp style URL: .PP \fBftp://@@:hostname/path/to/package.rpm\fP .PP If the \fB@@password\fP portion is omitted, the password will be prompted for (once per user/hostname pair). If both the user and password are omitted, anonymous ftp is used. In all cases passive (PASV) ftp transfers are used. RPM allows the folowing options to be used with ftp URLs: .IP "\fB\--ftpproxy \fP" The host will be used as a proxy server for all transfers, which allows users to ftp through firewall machines which use proxy systems. This option may also be specified in an \fIrpmrc\fP file. .IP "\fB\--ftpport \fP" Specifies the TCP port number to use for the ftp connection instead of the default port. This option may also be specified in an \fIrpmrc\fP file. @ 1.1.1.6 log @Import: RPM 2.3.11 @ text @d13 1 a13 1 There are ten basic modes of operation, and each takes a different d16 1 a16 2 \fIRebuild Database\fP, \fIfix permissions\fP, \fIset owners and groups\fR, and \fIShow RC\fP. d40 1 a40 17 .I "\fB rpm \-[b|t]\fIO\fB [build\-options] +\fP" .br Rebuild database: .br .I "\fB rpm \-\-rebuilddb" .br Fix permissions: .br .I "\fB rpm \-\-setperms [query\-package\-specifiers]\fP" .br Set owners and groups: .br .I "\fB rpm \-\-setugids [query\-package\-specifiers]\fP" .br Show RC: .br .I "\fB rpm \-\-showrc" d151 1 a151 1 .IP "\fB\-\-whatrequires \fI\fP" d153 1 a153 1 .IP "\fB\-\-whatprovides \fI\fP" d157 2 d164 2 a249 3 .IP "\fB\-\-allmatches\fP" Remove all versions of the package which match \fI\fR. Normally an error is issued if \fI\fR matches multiple packages. d263 1 a263 1 \fBrpm \-[b|t]\fIO\fP [build\-options] +\fP d265 2 a266 5 The argument used is \fB-b\fR if a spec file is being used to build the package and \fB-t\fR if \fBRPM\fR should look inside of a gzipped (or compressed) tar file for the spec file to use. After the first argument, the next argument (\fIO\fR) specifies the stages of building and packaging to be done and is one of: d382 1 a382 1 \fBftp://:@@hostname/path/to/package.rpm\fP @ 1.1.1.7 log @Import: RPM 2.4.12 @ text @d2 1 a2 1 .TH rpm 8 "19 August 1997" "Red Hat Software" "Red Hat Linux" d76 2 a77 11 .IP "\fB\-\-root \fI\fP" Use the system rooted at \fI\fP for all operations. Note that this means the database will be read or modified under \fI\fP and any \fIpre\fP or \fIpost\fP scripts are run after a chroot() to \fI\fP. .IP "\fB\-\-dbpath \fP" Use RPM database in . .IP "\fB\-\-ftpproxy \fP" Use as an FTP proxy. See \fBFTP OPTIONS\fP. .IP "\fB\-\-ftpport \fP" Use as an the FTP port. See \fBFTP OPTIONS\fP. d79 1 a79 1 .SH INSTALL AND UPGRADE OPTIONS a83 9 This installs a new package. The general form of an rpm upgrade command is .PP \fBrpm \-U [install\-options] +\fP .PP This upgrades or installs the package currently installed to the version in the new RPM. This is the same as install, except all other version of the package are removed from the system. d105 4 a108 3 .IP "\fB\-\-allfiles\fP" Installs or upgradesall the missingok files in the package, regardless if they exist. d110 1 a110 1 Don't do a dependency check before installing to upgrading a package. d119 2 d124 5 a128 8 .IP "\fB\-\-prefix \fP" This sets the installation prefix to for relocatable packages. .IP "\fB\-\-ignorearch\fP" This allows installation or upgrading even if the architectures of the binary RPM and host don't match. .IP "\fB\-\-ignoreos\fP" This allows installation or upgrading even if the operating systems of the binary RPM and host don't match. d147 3 a149 5 \fBRPMTAG_\fP portion of the tag name may be omitted. Alternate output formats may be requested by following the tag with \fB:\fItypetag\fR. Currently, the following types are supported: \fBoctal\fR, \fBdate\fR, \fBshescape\fR, \fBperms\fR, \fBfflags\fR, and \fBdepflags\fR. d165 1 a165 1 Query installed package named \fB\fI\fP. d167 1 a167 1 Query all installed packages a189 2 .IP "\fB\-\-changelog\fP" Display change information for the package. @ 1.1.1.8 log @Import: RPM 2.5 @ text @d124 1 a124 1 Installs or upgrades all the missingok files in the package, regardless if a339 3 .IP "\fB\-\-rmsource\fP" Remove the sources and spec file after the build (may also be used standalone, eg. "\fBrpm \-\-rmsource foo.spec\fP"). @ 1.1.1.9 log @Import: RPM 2.5.6 @ text @d85 1 a85 1 Use as the FTP port. See \fBFTP OPTIONS\fP. a129 2 .IP "\fB\-\-notriggers\fP" Don't execute scripts which are triggered by the installation of this package. a193 3 .IP "\fB\-\-requiredby \fI\fP" Query all of the package which contain triggers scripts that are triggered by \fI\fR. a224 2 .IP "\fB\-\-triggers\fP" Display the trigger scripts, if any, which are contained in the package. a289 2 .IP "\fB\-\-notriggers\fP" Don't execute scripts which are triggered by the removal of this package. @ 1.1.1.10 log @Import: RPM 3.0 @ text @d2 1 a2 1 .TH rpm 8 "22 December 1998" "Red Hat Software" "Red Hat Linux" d13 5 a17 7 One of the following basic modes must be selected: \fIInitialize Database\fP, \fIRebuild Database\fP, \fIBuild Package\fP, \fIRecompile Package\fP, \fIBuild Package from Tarball\fP, \fIQuery\fP, \fIShow Querytags\fP, \fIInstall\fP, \fIFreshen\fP, \fIUninstall\fP, \fIVerify\fP, \fISignature Check\fP, \fIResign\fP, \fIAdd Signature\fP, \fIset owners and groups\fR and \fIShow Configuration\fP. d19 1 a19 3 Database maintenance: d21 1 a21 1 .I "\fB rpm \-i [\-\-initdb]\fP" d23 1 a23 3 .I "\fB rpm \-i [\-\-rebuilddb]\fP" Building: d25 1 a25 1 .I "\fB rpm [\-b|t] [package_spec]+\fP" d27 1 a27 1 .I "\fB rpm [\-\-rebuild] [sourcerpm]+\fP" d29 1 a29 1 .I "\fB rpm [\-\-tarbuild] [tarredsource]+\fP" d31 1 a31 2 Querying: d33 1 a33 6 .I "\fB rpm [\-\-query] [queryoptions]\fP" .br .I "\fB rpm [\-\-querytags]\fP" .br Maintaining installed packages: d35 1 a35 1 .I "\fB rpm [\-\-install] [installoptions] [package_file]+\fP" d37 1 a37 1 .I "\fB rpm [\-\-freshen|\-F] [installoptions] [package_file]+\fP" d39 1 a39 1 .I "\fB rpm [\-\-uninstall|\-e] [uninstalloptions] [package]+\fP" d41 1 a41 1 .I "\fB rpm [\-\-verify|\-V] [verifyoptions] [package]+\fP" d43 1 a43 2 Signatures: d45 1 a45 1 .I "\fB rpm [\-\-verify|\-V] [verifyoptions] [package]+\fP" d47 1 a47 1 .I "\fB rpm [\-\-resign] [package_file]+\fP" d49 1 a49 1 .I "\fB rpm [\-\-addsign] [package_file]+\fP" d51 1 a51 2 Miscellaneous: d53 1 a53 1 .I "\fB rpm [\-\-showrc]\fP" d55 1 a55 1 .I "\fB rpm [\-\-setperms] [package]+\fP" d57 1 a57 1 .I "\fB rpm [\-\-setgids] [package]+\fP" a59 1 d64 3 d73 3 a75 7 Print a single line containing the version number of \fBrpm\fP being used. .IP "\fB\-\-rcfile \fI\fP" Each of the files in the colon separated \fI\fP is read sequentially by \fBrpm\fP for configuration information. The default \fI\fP is \fB/usr/lib/rpm/rpmrc:/etc/rpmrc:~/.rpmrc\fP. Only the first file in the list must exist, and tildes will be expanded to the value of \fB$HOME\fP. d80 7 a86 12 .IP "\fB\-\-dbpath \fI\fP" Use RPM database in \fI\fP. .IP "\fB\-\-justdb\fP" Update only the database, not the filesystem. .IP "\fB\-\-ftpproxy \fI\fP, \fB\-\-httpproxy \fI\fP" Use \fI\fP as an FTP or HTTP proxy host. See \fBFTP/HTTP OPTIONS\fP. .IP "\fB\-\-ftpport \fI\fP, \fB\-\-httpport \fI\fP" Use \fI\fP as the FTP or HTTP port on the proxy host. See \fBFTP/HTTP OPTIONS\fP. .IP "\fB\-\-pipe \fI\fP" Pipes the output of \fBrpm\fP to the command \fI\fP. d91 1 a91 1 \fBrpm \-i [install\-options] \fI+\fP d96 1 a96 1 \fBrpm \-U [install\-options] \fI+\fP a100 6 .PP \fBrpm [\-F|--freshen] [install\-options] \fI+\fP .PP This will upgrade packages, but only if an earlier version currently exists. d102 3 a104 3 The \fI\fP may be specified as an ftp or http URL, in which case the package will be downloaded before being installed. See \fBFTP/HTTP OPTIONS\fP for information on RPM's built-in ftp and http support. d107 3 a109 3 Same as using \fB\-\-replacepkgs\fP, \fB\-\-replacefiles\fP, and \fB\-\-oldpackage\fP. .IP "\fB\-h\fP, \fB\-\-hash\fP" d127 1 a127 1 Don't do a dependency check before installing or upgrading a package. a131 4 .IP "\fB\-\-ignoresize\fP" Don't check mount file systems for sufficient disk space before installing this package. .IP "\fB\-\-excludepath \fI\fP" Don't install files whose name begins with \fI\fP. d136 2 a137 1 Install documentation files. This is the default behavior. d141 2 a148 11 .IP "\fB\-\-prefix \fI\fP" This sets the installation prefix to \fI\fP for relocatable packages. .IP "\fB\-\-relocate \fI\fB=\fI\fP" For relocatable packages, translates the files that would be put in \fI\fP to \fI\fP. .IP "\fB\-\-badreloc\fP" To be used in conjunction with \-\-relocate, this forces the relocation even if the package isn't relocatable. .IP "\fB\-\-noorder\fP" Don't reorder the packages for an install. The list of packages would normally be reordered to satisfy dependancies. d157 2 a158 2 in. To do this, you use the \fB[\-\-queryformat|\-qf]\fP option, followed by the format string. d187 2 a188 2 Query installed package named \fI\fP. .IP "\fB\-a\fP, \fB\-\-all\fP" d194 1 a194 1 .IP "\fB\-f \fI\fP, \fB\-\-file \fI\fP" d196 3 a198 2 .IP "\fB\-g \fI\fP, \fB\-\-group \fI\fP" Query packages with the group of \fI\fP. d201 3 a203 13 The \fI\fP may be specified as an ftp or http style URL, in which case the package header will be downloaded and queried. See \fBFTP/HTTP OPTIONS\fP for information on RPM's built-in ftp and http client support. .IP "\fB\-\-specfile \fI\fP" Parse and query \fI\fP as if it were a package. Although not all the information (e.g. file lists) is available, this type of query permits rpm to be used to extract information from spec files without having to write a specfile parser. .IP "\fB\-\-querybynumber \fI\fP" Query the \fI\fPth database entry directly; this is helpful for debugging purposes. .IP "\fB\-\-triggeredby \fI\fP" Query packages that are triggered by packages \fI\fP. d211 2 a212 2 .IP "\fB\-R\fP, \fB\-\-requires\fP" List packages on which this package depends. d217 1 a217 1 .IP "\fB\-l\fP, \fB\-\-list\fP" d219 1 a219 1 .IP "\fB\-s\fP, \fB\-\-state\fP" d223 1 a223 1 .IP "\fB\-d\fP, \fB\-\-docfiles\fP" d225 1 a225 1 .IP "\fB\-c\fP, \fB\-\-configfiles\fP" d230 1 a230 1 .IP "\fB\-\-triggers\fP, \fB\-\-triggerscripts\fP" a235 7 .IP "\fB\-\-last\fP" Orders the package listing by install time such that the latest packages are at the top. .IP "\fB\-\-querybypkg\fP" This lists all the files in each package. .IP "\fB\-\-triggerscripts\fP" Shows all the trigger scripts for the selected packages. a252 12 Options that can be used in verify mode: .IP "\fB\-\-nofiles\fP" Ignores missing files when verifying. .IP "\fB\-\-nomd5\fP" Ignores MD5 checksum errors when verifying. .IP "\fB\-\-nopgp\fP" Ignores PGP checking errors when verifying. .IP "\fB\-\-nofiles\fP" Ignores missing files when verifying. d280 1 a280 1 \fBrpm \-\-checksig \fI+\fP d282 3 a284 3 This checks the PGP signature of package \fI\fP to ensure its integrity and origin. PGP configuration information is read from configuration files. d290 1 a290 1 \fB rpm \-e \fI+\fP d302 4 a305 2 Don't really uninstall anything, just go through the motions. Useful in conjunction with the \fB\-vv\fP option. d310 1 a310 1 \fBrpm \-[b|t]\fIO\fP [build\-options] \fI+\fP d323 2 a324 2 is macro expanded, and checks are made to verify that each file exists. a333 3 .IP "\fB\-bs\fP" Build just the source package (after doing the prep, build, and install stages). d344 3 a346 3 be configured by defining the macro "_timecheck". The timecheck value expresses, in seconds, the maximum age of a file being packaged. Warnings will be printed for all files beyond the timecheck age. d358 1 a358 15 section on PGP SIGNATURES for configuration details. .IP "\fB\-\-buildroot \fI\fP" When building the package, override the BuildRoot tag with directory \fI\fP. .IP "\fB\-\-target \fI\fP" When building the package, interpret \fI\fP as \fBarch-vendor-os\fP and set the macros \fB_target\fP, \fB_target_arch\fP and \fB_target_os\fP accordingly. .IP "\fB\-\-buildarch \fI\fP" When building the package, set the architecture to \fI\fP. This option has been obsoleted by \fB\-\-target\fI in RPM 3.0. .IP "\fB\-\-buildos \fI\fP" When building the package, set the architecture to \fI\fP. This option has been obsoleted by \fB\-\-target\fI in RPM 3.0. d362 1 a362 1 There are two other ways to invoke building with rpm: d364 1 a364 1 .I "\fBrpm \-\-recompile \fI+\fP" d366 1 a366 1 .I "\fBrpm \-\-rebuild \fI+\fP" d368 1 a368 1 When invoked this way, \fBrpm\fP installs the named source package, and does d376 1 a376 1 .I "\fBrpm \-\-resign \fI+\fP" a380 5 .I "\fBrpm \-\-addsign \fI+\fP" This option generates and appends new signatures for the listed packages to those that already exist. d388 1 a388 1 you will need to configure the macro d390 2 a391 2 .IP "\fB_pgp_path\fP" to be the location of the PGP key rings to use. d396 1 a396 1 You will also need to configure the macros d398 1 a398 1 .IP "\fB_signature\fP" d400 1 a400 1 .IP "\fB_pgp_name\fP" a407 15 For example, to be able to use PGP to sign packages as the user \fp"John Doe "\fP from the key rings located in \fB/etc/rpm/.pgp\fP you would include .IP "\fB%_signature\fP" \fBpgp\fP .IP "\fB%_pgp_name\fP" \fB/etc/rpm/.pgp\fP .IP "\fB%_pgp_name\fP" \fBJohn Doe " .PP in a macro configuration file. Use \fB/etc/rpm/macros\fP for per-system configuration and \fB~/.rpmmacros\fP for per-user configuration. d415 1 a415 7 To rebuild a new database, do: .PP \fBrpm \-\-initdb\fP .PP The only options for these modes are \fB-\-dbpath\fP and \fB-\-root\fP. d428 1 a428 1 .SH FTP/HTTP OPTIONS d430 3 a432 3 RPM includes simple FTP and HTTP clients to simplify installing and querying packages which are available over the internet. Package files for install, upgrade, and query operations may be specified as an ftp or http style URL: d435 1 a435 1 \fBftp://:@@hostname:/path/to/package.rpm\fP d437 1 a437 1 If the \fB:password\fP portion is omitted, the password will be prompted d442 1 a442 1 RPM allows the following options to be used with ftp URLs: d444 9 a452 24 .IP "\fB\--ftpproxy \fI\fP" The host \fI\fP will be used as a proxy server for all ftp transfers, which allows users to ftp through firewall machines which use proxy systems. This option may also be specified by configuring the macro \fB_ftpproxy\fP. .IP "\fB\--ftpport \fI\fP" The TCP \fI\fP number to use for the ftp connection on the proxy ftp server instead of the default port. This option may also be specified by configuring the macro \fB_ftpport\fP. .PP RPM allows the following options to be used with http URLs: .IP "\fB\--httpproxy \fI\fP" The host \fI\fP will be used as a proxy server for all http transfers. This option may also be specified by configuring the macro \fB_httpproxy\fP. .IP "\fB\--httpport \fI\fP" The TCP \fI\fP number to use for the http connection on the proxy http server instead of the default port. This option may also be specified by configuring the macro \fB_httpport\fP. .PP a455 1 /usr/lib/rpm/rpmrc d467 1 a467 1 .B http://www.rpm.org/ a471 1 Jeff Johnson @ 1.1.1.11 log @Import: RPM 3.0.1 @ text @d287 1 a287 1 .IP "\fB\-\-filesbypkg\fP" d470 4 a473 3 In order to use the signature feature RPM must be configured to run PGP, and it must be able to find a public key ring with RPM public keys in it. By default, RPM uses the PGP defaults to find the keyrings (honoring PGPPATH). @