rpmgraph(8) [debian man page]

RPMGRAPH(8)						      System Manager's Manual						       RPMGRAPH(8)

NAME

       rpmgraph - Display RPM Package Dependency Graph

SYNOPSIS

       rpmgraph PACKAGE_FILE ...

DESCRIPTION

       rpmgraph  uses PACKAGE_FILE arguments to generate a package dependency graph. Each PACKAGE_FILE argument is read and added to an rpm trans-
       action set. The elements of the transaction set are partially ordered using a topological sort. The partially  ordered  elements  are  then
       printed to standard output.

       Nodes  in  the  dependency  graph  are  package names, and edges in the directed graph point to the parent of each node. The parent node is
       defined as the last predecessor of a package when partially ordered using the package dependencies as a relation. That means that the  par-
       ent of a given package is the package's last prerequisite.

       The  output  is	in  dot(1)  directed graph format, and can be displayed or printed using the dotty graph editor from the graphviz package.
       There are no rpmgraph specific options, only common rpm options.  See the rpmgraph usage message for what is currently implemented.

SEE ALSO

       dot(1),

       dotty(1),

	http://www.graphviz.org/ <URL:http://www.graphviz.org/>

AUTHORS

       Jeff Johnson <jbj@redhat.com>

Red Hat, Inc.							   30 June 2002 						       RPMGRAPH(8)

RPMKEYS(8)						      System Manager's Manual							RPMKEYS(8)

NAME

       rpmkeys - RPM Keyring

SYNOPSIS

       rpmkeys {--import|--checksig}

DESCRIPTION

       The general forms of rpm digital signature commands are

       rpmkeys --import PUBKEY ...

       rpmkeys {-K|--checksig} PACKAGE_FILE ...

       The  --checksig	option	checks all the digests and signatures contained in PACKAGE_FILE to ensure the integrity and origin of the package.
       Note that signatures are now verified whenever a package is read, and --checksig is useful to verify all  of  the  digests  and	signatures
       associated with a package.

       Digital	signatures  cannot be verified without a public key.  An ASCII armored public key can be added to the rpm database using --import.
       An imported public key is carried in a header, and key ring management is performed exactly like package management. For example, all  cur-
       rently imported public keys can be displayed by:

       rpm -qa gpg-pubkey*

       Details about a specific public key, when imported, can be displayed by querying.  Here's information about the Red Hat GPG/DSA key:

       rpm -qi gpg-pubkey-db42a60e

       Finally, public keys can be erased after importing just like packages. Here's how to remove the Red Hat GPG/DSA key

       rpm -e gpg-pubkey-db42a60e

SEE ALSO

       popt(3),
       rpm(8),
       rpmdb(8),
       rpmsign(8),
       rpm2cpio(8),
       rpmbuild(8),
       rpmspec(8),

       rpmkeys	--help - as rpm supports customizing the options via popt aliases it's impossible to guarantee that what's described in the manual
       matches what's available.

       http://www.rpm.org/ <URL:http://www.rpm.org/>

AUTHORS

       Marc Ewing <marc@redhat.com>
       Jeff Johnson <jbj@redhat.com>
       Erik Troan <ewt@redhat.com>
       Panu Matilainen <pmatilai@redhat.com>

Red Hat, Inc							  29 October 2010							RPMKEYS(8)