1RPM(8) System Manager's Manual RPM(8)
2
6 rpm - RPM Package Manager
7
9 QUERYING AND VERIFYING PACKAGES:
10 rpm {-q|--query} [select-options] [query-options]
11 rpm {-V|--verify} [select-options] [verify-options]
15 rpm --import PUBKEY ...
19 rpm {-K|--checksig} [--nosignature] [--nodigest]
23 PACKAGE_FILE ...
24 INSTALLING, UPGRADING, AND REMOVING PACKAGES:
27 rpm {-i|--install} [install-options] PACKAGE_FILE ...
28 rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
32 rpm {-F|--freshen} [install-options] PACKAGE_FILE ...
36 rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts]
40 [--notriggers] [--test] PACKAGE_NAME ...
41 MISCELLANEOUS:
44 rpm {--initdb|--rebuilddb}
45 rpm {--addsign|--resign} PACKAGE_FILE ...
49 rpm {--querytags|--showrc}
53 rpm {--setperms|--setugids} PACKAGE_NAME ...
57 select-options
60 [PACKAGE_NAME] [-a,--all] [-f,--file FILE]
61 [-g,--group GROUP] {-p,--package PACKAGE_FILE]
62 [--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID]
63 [--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME]
64 [--whatprovides CAPABILITY] [--whatrequires CAPABILITY]
65 query-options
68 [--changelog] [-c,--configfiles] [--conflicts]
69 [-d,--docfiles] [--dump] [--filesbypkg] [-i,--info]
70 [--last] [-l,--list] [--provides]
71 [--qf,--queryformat QUERYFMT] [-R,--requires]
72 [--scripts] [-s,--state] [--triggers,--triggerscripts]
73 verify-options
76 [--nodeps] [--nofiles] [--noscripts]
77 [--nodigest] [--nosignature]
78 [--nolinkto] [--nofiledigest] [--nosize] [--nouser]
79 [--nogroup] [--nomtime] [--nomode] [--nordev]
80 [--nocaps]
81 install-options
84 [--aid] [--allfiles] [--badreloc] [--excludepath OLDPATH]
85 [--excludedocs] [--force] [-h,--hash]
86 [--ignoresize] [--ignorearch] [--ignoreos]
87 [--includedocs] [--justdb] [--nodeps]
88 [--nodigest] [--nosignature] [--nosuggest]
89 [--noorder] [--noscripts] [--notriggers]
90 [--oldpackage] [--percent] [--prefix NEWPATH]
91 [--relocate OLDPATH=NEWPATH]
92 [--replacefiles] [--replacepkgs]
93 [--test]
94
97 rpm is a powerful Package Manager, which can be used to build, install,
98 query, verify, update, and erase individual software packages. A pack‐
99 age consists of an archive of files and meta-data used to install and
100 erase the archive files. The meta-data includes helper scripts, file
101 attributes, and descriptive information about the package. Packages
102 come in two varieties: binary packages, used to encapsulate software to
103 be installed, and source packages, containing the source code and
104 recipe necessary to produce binary packages.
105 One of the following basic modes must be selected: Query, Verify, Sig‐
107 nature Check, Install/Upgrade/Freshen, Uninstall, Initialize Database,
108 Rebuild Database, Resign, Add Signature, Set Owners/Groups, Show Query‐
109 tags, and Show Configuration.
110 GENERAL OPTIONS
112 These options can be used in all the different modes.
113 -?, --help
115 Print a longer usage message then normal.
116 --version
118 Print a single line containing the version number of rpm being
119 used.
120 --quiet
122 Print as little as possible - normally only error messages will
123 be displayed.
124 -v Print verbose information - normally routine progress messages
126 will be displayed.
127 -vv Print lots of ugly debugging information.
129 --rcfile FILELIST
131 Each of the files in the colon separated FILELIST is read
132 sequentially by rpm for configuration information. Only the
133 first file in the list must exist, and tildes will be expanded
134 to the value of $HOME. The default FILELIST is
135 /usr/lib/rpm/rpmrc:/usr/lib/rpm/red‐
136 hat/rpmrc:/etc/rpmrc:~/.rpmrc.
137 --pipe CMD
139 Pipes the output of rpm to the command CMD.
140 --dbpath DIRECTORY
142 Use the database in DIRECTORY rather than the default path
143 /var/lib/rpm
144 --root DIRECTORY
146 Use the file system tree rooted at DIRECTORY for all operations.
147 Note that this means the database within DIRECTORY will be used
148 for dependency checks and any scriptlet(s) (e.g. %post if
149 installing, or %prep if building, a package) will be run after a
150 chroot(2) to DIRECTORY.
151 INSTALL AND UPGRADE OPTIONS
153 In these options, PACKAGE_FILE can be either rpm binary file or ASCII
154 package manifest (see PACKAGE SELECTION OPTIONS), and may be specified
155 as an ftp or http URL, in which case the package will be downloaded
156 before being installed. See FTP/HTTP OPTIONS for information on rpm's
157 internal ftp and http client support.
158 The general form of an rpm install command is
160 rpm {-i|--install} [install-options] PACKAGE_FILE ...
162 This installs a new package.
164 The general form of an rpm upgrade command is
166 rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
168 This upgrades or installs the package currently installed to a newer
170 version. This is the same as install, except all other version(s) of
171 the package are removed after the new package is installed.
172 rpm {-F|--freshen} [install-options] PACKAGE_FILE ...
174 This will upgrade packages, but only ones for which an earlier version
176 is installed.
177 --aid Add suggested packages to the transaction set when needed.
179 --allfiles
181 Installs or upgrades all the missingok files in the package,
182 regardless if they exist.
183 --badreloc
185 Used with --relocate, permit relocations on all file paths, not
186 just those OLDPATH's included in the binary package relocation
187 hint(s).
188 --excludepath OLDPATH
190 Don't install files whose name begins with OLDPATH.
191 --excludedocs
193 Don't install any files which are marked as documentation (which
194 includes man pages and texinfo documents).
195 --force
197 Same as using --replacepkgs, --replacefiles, and --oldpackage.
198 -h, --hash
200 Print 50 hash marks as the package archive is unpacked. Use
201 with -v|--verbose for a nicer display.
202 --ignoresize
204 Don't check mount file systems for sufficient disk space before
205 installing this package.
206 --ignorearch
208 Allow installation or upgrading even if the architectures of the
209 binary package and host don't match.
210 --ignoreos
212 Allow installation or upgrading even if the operating systems of
213 the binary package and host don't match.
214 --includedocs
216 Install documentation files. This is the default behavior.
217 --justdb
219 Update only the database, not the filesystem.
220 --nodigest
222 Don't verify package or header digests when reading.
223 --nomanifest
225 Don't process non-package files as manifests.
226 --nosignature
228 Don't verify package or header signatures when reading.
229 --nodeps
231 Don't do a dependency check before installing or upgrading a
232 package.
233 --nosuggest
235 Don't suggest package(s) that provide a missing dependency.
236 --noorder
238 Don't reorder the packages for an install. The list of packages
239 would normally be reordered to satisfy dependencies.
240 --noscripts
242 --nopre
244 --nopost
246 --nopreun
248 --nopostun
250 Don't execute the scriptlet of the same name. The --noscripts
251 option is equivalent to
252 --nopre --nopost --nopreun --nopostun
254 and turns off the execution of the corresponding %pre, %post,
256 %preun, and %postun scriptlet(s).
257 --notriggers
259 --notriggerin
261 --notriggerun
263 --notriggerpostun
265 Don't execute any trigger scriptlet of the named type. The
266 --notriggers option is equivalent to
267 --notriggerin --notriggerun --notriggerpostun
269 and turns off execution of the corresponding %triggerin, %trig‐
271 gerun, and %triggerpostun scriptlet(s).
272 --oldpackage
274 Allow an upgrade to replace a newer package with an older one.
275 --percent
277 Print percentages as files are unpacked from the package ar‐
278 chive. This is intended to make rpm easy to run from other
279 tools.
280 --prefix NEWPATH
282 For relocatable binary packages, translate all file paths that
283 start with the installation prefix in the package relocation
284 hint(s) to NEWPATH.
285 --relocate OLDPATH=NEWPATH
287 For relocatable binary packages, translate all file paths that
288 start with OLDPATH in the package relocation hint(s) to NEWPATH.
289 This option can be used repeatedly if several OLDPATH's in the
290 package are to be relocated.
291 --replacefiles
293 Install the packages even if they replace files from other,
294 already installed, packages.
295 --replacepkgs
297 Install the packages even if some of them are already installed
298 on this system.
299 --test Do not install the package, simply check for and report poten‐
301 tial conflicts.
302 ERASE OPTIONS
304 The general form of an rpm erase command is
305 rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers]
307 [--test] PACKAGE_NAME ...
308 The following options may also be used:
311 --allmatches
313 Remove all versions of the package which match PACKAGE_NAME.
314 Normally an error is issued if PACKAGE_NAME matches multiple
315 packages.
316 --nodeps
318 Don't check dependencies before uninstalling the packages.
319 --noscripts
321 --nopreun
323 --nopostun
325 Don't execute the scriptlet of the same name. The --noscripts
326 option during package erase is equivalent to
327 --nopreun --nopostun
329 and turns off the execution of the corresponding %preun, and
331 %postun scriptlet(s).
332 --notriggers
334 --notriggerun
336 --notriggerpostun
338 Don't execute any trigger scriptlet of the named type. The
339 --notriggers option is equivalent to
340 --notriggerun --notriggerpostun
342 and turns off execution of the corresponding %triggerun, and
344 %triggerpostun scriptlet(s).
345 --test Don't really uninstall anything, just go through the motions.
347 Useful in conjunction with the -vv option for debugging.
348 QUERY OPTIONS
350 The general form of an rpm query command is
351 rpm {-q|--query} [select-options] [query-options]
353 You may specify the format that package information should be printed
356 in. To do this, you use the
357 --qf|--queryformat QUERYFMT
359 option, followed by the QUERYFMT format string. Query formats are mod‐
361 ified versions of the standard printf(3) formatting. The format is made
362 up of static strings (which may include standard C character escapes
363 for newlines, tabs, and other special characters) and printf(3) type
364 formatters. As rpm already knows the type to print, the type specifier
365 must be omitted however, and replaced by the name of the header tag to
366 be printed, enclosed by {} characters. Tag names are case insensitive,
367 and the leading RPMTAG_ portion of the tag name may be omitted as well.
368 Alternate output formats may be requested by following the tag with
370 :typetag. Currently, the following types are supported:
371 :armor Wrap a public key in ASCII armor.
373 :arraysize
375 Display number of elements in array tags.
376 :base64
378 Encode binary data using base64.
379 :date Use strftime(3) "%c" format.
381 :day Use strftime(3) "%a %b %d %Y" format.
383 :depflags
385 Format dependency comparison operator.
386 :deptype
388 Format dependency type.
389 :fflags
391 Format file flags.
392 :fstate
394 Format file state.
395 :hex Format in hexadecimal.
397 :octal Format in octal.
399 :perms Format file permissions.
401 :pgpsig
403 Display signature fingerprint and time.
404 :shescape
406 Escape single quotes for use in a script.
407 :triggertype
409 Display trigger suffix.
410 :vflags
412 File verification flags.
413 :xml Wrap data in simple xml markup.
415 For example, to print only the names of the packages queried, you could
417 use %{NAME} as the format string. To print the packages name and dis‐
418 tribution information in two columns, you could use %-30{NAME}%{DISTRI‐
419 BUTION}. rpm will print a list of all of the tags it knows about when
420 it is invoked with the --querytags argument.
421 There are two subsets of options for querying: package selection, and
423 information selection.
424 PACKAGE SELECTION OPTIONS:
426 PACKAGE_NAME
427 Query installed package named PACKAGE_NAME.
428 -a, --all
430 Query all installed packages.
431 -f, --file FILE
433 Query package owning FILE.
434 --fileid MD5
436 Query package that contains a given file identifier, i.e. the
437 MD5 digest of the file contents.
438 -g, --group GROUP
440 Query packages with the group of GROUP.
441 --hdrid SHA1
443 Query package that contains a given header identifier, i.e. the
444 SHA1 digest of the immutable header region.
445 -p, --package PACKAGE_FILE
447 Query an (uninstalled) package PACKAGE_FILE. The PACKAGE_FILE
448 may be specified as an ftp or http style URL, in which case the
449 package header will be downloaded and queried. See FTP/HTTP
450 OPTIONS for information on rpm's internal ftp and http client
451 support. The PACKAGE_FILE argument(s), if not a binary package,
452 will be interpreted as an ASCII package manifest unless --noman‐
453 ifest option is used. In manifests, comments are permitted,
454 starting with a '#', and each line of a package manifest file
455 may include white space separated glob expressions, including
456 URL's, that will be expanded to paths that are substituted in
457 place of the package manifest as additional PACKAGE_FILE argu‐
458 ments to the query.
459 --pkgid MD5
461 Query package that contains a given package identifier, i.e. the
462 MD5 digest of the combined header and payload contents.
463 --querybynumber HDRNUM
465 Query the HDRNUMth database entry directly; this is useful only
466 for debugging.
467 --specfile SPECFILE
469 Parse and query SPECFILE as if it were a package. Although not
470 all the information (e.g. file lists) is available, this type of
471 query permits rpm to be used to extract information from spec
472 files without having to write a specfile parser.
473 --tid TID
475 Query package(s) that have a given TID transaction identifier. A
476 unix time stamp is currently used as a transaction identifier.
477 All package(s) installed or erased within a single transaction
478 have a common identifier.
479 --triggeredby PACKAGE_NAME
481 Query packages that are triggered by package(s) PACKAGE_NAME.
482 --whatprovides CAPABILITY
484 Query all packages that provide the CAPABILITY capability.
485 --whatrequires CAPABILITY
487 Query all packages that require CAPABILITY for proper function‐
488 ing.
489 PACKAGE QUERY OPTIONS:
491 --changelog
492 Display change information for the package.
493 -c, --configfiles
495 List only configuration files (implies -l).
496 --conflicts
498 List capabilities this package conflicts with.
499 -d, --docfiles
501 List only documentation files (implies -l).
502 --dump Dump file information as follows (implies -l):
504 path size mtime filedigest mode owner group isconfig isdoc rdev symlink
507 --filesbypkg
510 List all the files in each selected package.
511 -i, --info
513 Display package information, including name, version, and
514 description. This uses the --queryformat if one was specified.
515 --last Orders the package listing by install time such that the latest
517 packages are at the top.
518 -l, --list
520 List files in package.
521 --provides
523 List capabilities this package provides.
524 -R, --requires
526 List capabilities on which this package depends.
527 --scripts
529 List the package specific scriptlet(s) that are used as part of
530 the installation and uninstallation processes.
531 -s, --state
533 Display the states of files in the package (implies -l). The
534 state of each file is one of normal, not installed, or replaced.
535 --triggers, --triggerscripts
537 Display the trigger scripts, if any, which are contained in the
538 package.
539 VERIFY OPTIONS
541 The general form of an rpm verify command is
542 rpm {-V|--verify} [select-options] [verify-options]
544 Verifying a package compares information about the installed files in
547 the package with information about the files taken from the package
548 metadata stored in the rpm database. Among other things, verifying
549 compares the size, MD5 sum, permissions, type, owner and group of each
550 file. Any discrepancies are displayed. Files that were not installed
551 from the package, for example, documentation files excluded on instal‐
552 lation using the "--excludedocs" option, will be silently ignored.
553 The package selection options are the same as for package querying
555 (including package manifest files as arguments). Other options unique
556 to verify mode are:
557 --nodeps
559 Don't verify dependencies of packages.
560 --nodigest
562 Don't verify package or header digests when reading.
563 --nofiles
565 Don't verify any attributes of package files.
566 --noscripts
568 Don't execute the %verifyscript scriptlet (if any).
569 --nosignature
571 Don't verify package or header signatures when reading.
572 --nolinkto
574 --nofiledigest (formerly --nomd5)
576 --nosize
578 --nouser
580 --nogroup
582 --nomtime
584 --nomode
586 --nordev
588 Don't verify the corresponding file attribute.
589 The format of the output is a string of 8 characters, a possible
591 attribute marker:
592 c %config configuration file.
594 d %doc documentation file.
595 g %ghost file (i.e. the file contents are not included in the package payload).
596 l %license license file.
597 r %readme readme file.
598 from the package header, followed by the file name. Each of the 8
600 characters denotes the result of a comparison of attribute(s) of the
601 file to the value of those attribute(s) recorded in the database. A
602 single "." (period) means the test passed, while a single "?" (question
603 mark) indicates the test could not be performed (e.g. file permissions
604 prevent reading). Otherwise, the (mnemonically emBoldened) character
605 denotes failure of the corresponding --verify test:
606 S file Size differs
608 M Mode differs (includes permissions and file type)
609 5 MD5 sum differs
610 D Device major/minor number mismatch
611 L readL[22mink(2) path mismatch
612 U User ownership differs
613 G Group ownership differs
614 T mTime differs
615 P caPabilities differ
616 DIGITAL SIGNATURE AND DIGEST VERIFICATION
619 The general forms of rpm digital signature commands are
620 rpm --import PUBKEY ...
622 rpm {--checksig} [--nosignature] [--nodigest]
625 PACKAGE_FILE ...
626 The --checksig option checks all the digests and signatures contained
629 in PACKAGE_FILE to ensure the integrity and origin of the package. Note
630 that signatures are now verified whenever a package is read, and
631 --checksig is useful to verify all of the digests and signatures asso‐
632 ciated with a package.
633 Digital signatures cannot be verified without a public key. An ASCII
635 armored public key can be added to the rpm database using --import. An
636 imported public key is carried in a header, and key ring management is
637 performed exactly like package management. For example, all currently
638 imported public keys can be displayed by:
639 rpm -qa gpg-pubkey*
641 Details about a specific public key, when imported, can be displayed by
643 querying. Here's information about the Red Hat GPG/DSA key:
644 rpm -qi gpg-pubkey-db42a60e
646 Finally, public keys can be erased after importing just like packages.
648 Here's how to remove the Red Hat GPG/DSA key
649 rpm -e gpg-pubkey-db42a60e
651 SIGNING A PACKAGE
653 rpm --addsign|--resign PACKAGE_FILE ...
654 Both of the --addsign and --resign options generate and insert new sig‐
657 natures for each package PACKAGE_FILE given, replacing any existing
658 signatures. There are two options for historical reasons, there is no
659 difference in behavior currently.
660 USING GPG TO SIGN PACKAGES
662 In order to sign packages using GPG, rpm must be configured to run GPG
663 and be able to find a key ring with the appropriate keys. By default,
664 rpm uses the same conventions as GPG to find key rings, namely the
665 $GNUPGHOME environment variable. If your key rings are not located
666 where GPG expects them to be, you will need to configure the macro
667 %_gpg_path to be the location of the GPG key rings to use.
668 For compatibility with older versions of GPG, PGP, and rpm, only V3
670 OpenPGP signature packets should be configured. Either DSA or RSA ver‐
671 ification algorithms can be used, but DSA is preferred.
672 If you want to be able to sign packages you create yourself, you also
674 need to create your own public and secret key pair (see the GPG man‐
675 ual). You will also need to configure the rpm macros
676 %_signature
678 The signature type. Right now only gpg and pgp are supported.
679 %_gpg_name
681 The name of the "user" whose key you wish to use to sign your
682 packages.
683 For example, to be able to use GPG to sign packages as the user "John
685 Doe <jdoe@foo.com>" from the key rings located in /etc/rpm/.gpg using
686 the executable /usr/bin/gpg you would include
687 %_signature gpg
689 %_gpg_path /etc/rpm/.gpg
690 %_gpg_name John Doe <jdoe@foo.com>
691 %__gpg /usr/bin/gpg
692 in a macro configuration file. Use /etc/rpm/macros for per-system con‐
694 figuration and ~/.rpmmacros for per-user configuration. Typically it's
695 sufficient to set just %_gpg_name.
696 REBUILD DATABASE OPTIONS
698 The general form of an rpm rebuild database command is
699 rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY]
701 Use --initdb to create a new database if one doesn't already exist
704 (existing database is not overwritten), use --rebuilddb to rebuild the
705 database indices from the installed package headers.
706 SHOWRC
708 The command
709 rpm --showrc
711 shows the values rpm will use for all of the options are currently set
713 in rpmrc and macros configuration file(s).
714 FTP/HTTP OPTIONS
716 rpm can act as an FTP and/or HTTP client so that packages can be
717 queried or installed from the internet. Package files for install,
718 upgrade, and query operations may be specified as an ftp or http style
719 URL:
720 ftp://USER:PASSWORD@HOST:PORT/path/to/package.rpm
722 If the :PASSWORD portion is omitted, the password will be prompted for
724 (once per user/hostname pair). If both the user and password are omit‐
725 ted, anonymous ftp is used. In all cases, passive (PASV) ftp transfers
726 are performed.
727 rpm allows the following options to be used with ftp URLs:
729 --ftpproxy HOST
731 The host HOST will be used as a proxy server for all ftp trans‐
732 fers, which allows users to ftp through firewall machines which
733 use proxy systems. This option may also be specified by config‐
734 uring the macro %_ftpproxy.
735 --ftpport PORT
737 The TCP PORT number to use for the ftp connection on the proxy
738 ftp server instead of the default port. This option may also be
739 specified by configuring the macro %_ftpport.
740 rpm allows the following options to be used with http URLs:
742 --httpproxy HOST
744 The host HOST will be used as a proxy server for all http trans‐
745 fers. This option may also be specified by configuring the macro
746 %_httpproxy.
747 --httpport PORT
749 The TCP PORT number to use for the http connection on the proxy
750 http server instead of the default port. This option may also be
751 specified by configuring the macro %_httpport.
752
754 Executing rpmbuild
755 The build modes of rpm are now resident in the /usr/bin/rpmbuild exe‐
756 cutable. Install the package containing rpmbuild (usually rpm-build)
757 and see rpmbuild(8) for documentation of all the rpm build modes.
758
760 rpmrc Configuration
761 /usr/lib/rpm/rpmrc
762 /usr/lib/rpm/redhat/rpmrc
763 /etc/rpmrc
764 ~/.rpmrc
765 Macro Configuration
767 /usr/lib/rpm/macros
768 /usr/lib/rpm/redhat/macros
769 /etc/rpm/macros
770 ~/.rpmmacros
771 Database
773 /var/lib/rpm/Basenames
774 /var/lib/rpm/Conflictname
775 /var/lib/rpm/Dirnames
776 /var/lib/rpm/Filemd5s
777 /var/lib/rpm/Group
778 /var/lib/rpm/Installtid
779 /var/lib/rpm/Name
780 /var/lib/rpm/Packages
781 /var/lib/rpm/Providename
782 /var/lib/rpm/Provideversion
783 /var/lib/rpm/Pubkeys
784 /var/lib/rpm/Removed
785 /var/lib/rpm/Requirename
786 /var/lib/rpm/Requireversion
787 /var/lib/rpm/Sha1header
788 /var/lib/rpm/Sigmd5
789 /var/lib/rpm/Triggername
790 Temporary
792 /var/tmp/rpm*
793
795 popt(3),
796 rpm2cpio(8),
797 rpmbuild(8),
798 rpm --help - as rpm supports customizing the options via popt aliases
800 it's impossible to guarantee that what's described in the manual
801 matches what's available.
802 http://www.rpm.org/ <URL:http://www.rpm.org/>
805
807 Marc Ewing <marc@redhat.com>
808 Jeff Johnson <jbj@redhat.com>
809 Erik Troan <ewt@redhat.com>
810Red Hat, Inc. 09 June 2002 RPM(8)