Linux-Noob Forums - Package Management

List and extract RPM files.

Sun, 05 Sep 2010 19:58:36 +0200

I did a lot of looking on-line and that was not helpful at all. I hope someone can explain how I can either extract all files from an RPM or only extract certain files from an RPM?

This is without installing the RPM file.

Thanks in advance,

Bakshara

Software Install with YUM

Sun, 26 Oct 2008 22:35:13 +0100

1. Overview

YUM extends RPM functionality by downloading and installing packages directly from online repositories. As well as all the advantages of RPM, YUM provides a few more handy features:

version compatibility: YUM will automatically locate the latest package version on that repo suited to your kernel
pre-requisites satisfied: any dependencies are automatically downloaded and installed first - solving that bugbear of "RPM dependency hell"
supports local installation: YUM can attempt to install a locally-held RPM package, satisfying pre-requisites online if necessary.
package updates: YUM can be instructed to update all installed software with only a few simple commands - or even scheduled to perform this automatically at regular intervals
repo index caching: YUM caches an index of repo packages, which can be interrogated to determine repo contents without going online - this can be used to search for packages, or determine what packages provide a required command - or even what are the dependencies for a specific package.
repo reports: YUM can report what repos are in effect, which is a bit clearer than trawling through directories of config files.
cache management: YUM downloads RPM packages into a cache area prior to installing; a few options to YUM can flush this cache to tidy up after itself

2. Basic Commands

1. Installing a package: yum install packagename(s), for example:

Code:
# yum install cacti

Loaded plugins: refresh-packagekit

Setting up Install Process

Parsing package install arguments

Resolving Dependencies

--> Running transaction check

---> Package cacti.noarch 0:0.8.7b-4.fc10 set to be updated

--> Processing Dependency: rrdtool for package: cacti

--> Processing Dependency: php-snmp for package: cacti

--> Processing Dependency: mysql for package: cacti

--> Running transaction check

---> Package rrdtool.i386 0:1.3.4-2.fc10 set to be updated

--> Processing Dependency: dejavu-lgc-fonts for package: rrdtool

---> Package mysql.i386 0:5.0.67-2.fc10 set to be updated

--> Processing Dependency: perl(DBI) for package: mysql

---> Package php-snmp.i386 0:5.2.6-5 set to be updated

--> Running transaction check

---> Package perl-DBI.i386 0:1.607-1.fc10 set to be updated

---> Package dejavu-lgc-fonts.noarch 0:2.26-2.fc10 set to be updated

--> Finished Dependency Resolution

Dependencies Resolved

================================================================================

Package                 Arch          Version              Repository     Size

================================================================================

Installing:

cacti                   noarch        0.8.7b-4.fc10        fedora        1.9 M

Installing for dependencies:

dejavu-lgc-fonts        noarch        2.26-2.fc10          fedora        3.5 M

mysql                   i386          5.0.67-2.fc10        fedora        3.1 M

perl-DBI                i386          1.607-1.fc10         fedora        776 k

php-snmp                i386          5.2.6-5              fedora         24 k

rrdtool                 i386          1.3.4-2.fc10         fedora        391 k

Transaction Summary

================================================================================

Install      6 Package(s)

Update       0 Package(s)

Remove       0 Package(s)

Total download size: 9.7 M

Is this ok [y/N]:

From here, just a simple answer of "Y" will begin downloading these six packages then install them automatically.

Tip: use the "-y" option on yum to answer "yes" to everything.

2. Using yum to install a locally-stored RPM file: yum localinstall rpm-package-file, for instance:

Code:
# yum localinstall wine-2.3.4.5

3. Updating a package: yum update packagename, eg:

Code:
# yum update sudo

Loaded plugins: refresh-packagekit

Setting up Update Process

Resolving Dependencies

--> Running transaction check

---> Package sudo.i386 0:1.6.9p17-4.fc10 set to be updated

--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================

Package       Arch          Version                  Repository        Size

=============================================================================

Updating:

sudo          i386          1.6.9p17-4.fc10          updates          225 k

Transaction Summary

=============================================================================

Install      0 Package(s)

Update       1 Package(s)

Remove       0 Package(s)

Total download size: 225 k

Is this ok [y/N]:

Tip: unlike the -U option to RPM, yum update will not update uninstalled packages. However, yum install will attempt to install a new package, or upgrade an already-installed one - use that option first!

4. Listing packages held on a repo: yum list searchterm will use that term as a filter, for example:

Code:
$ yum list yum

Loaded plugins: priorities

Excluding Packages in global exclude list

Finished

Installed Packages

yum.noarch                     3.2.19-3.fc8     installed

Available Packages

yum.noarch                     3.2.20-5.fc8      updates-newkey

Although yum version 3.2.19-3 is currently installed, a newer version (3.2.20-5) is available for updating.

5. Searching repos for packages: yum search package-to-search will look for packages matching that search term, eg:

Code:
# yum search sql

Loaded plugins: priorities

Excluding Packages in global exclude list

Finished

=================== Matched: sql ===========================

dovecot.i386 : Dovecot Secure imap server

dovecot-mysql.i386 : MySQL backend for dovecot

dovecot-pgsql.i386 : Postgres SQL backend for dovecot

dovecot-sqlite.i386 : SQLite backend for dovecot

hsqldb.i386 : Hsqldb Database Engine

hsqldb-demo.i386 : Demo for hsqldb

hsqldb-javadoc.i386 : Javadoc for hsqldb

hsqldb-manual.i386 : Manual for hsqldb

koffice-kexi-driver-mysql.i386 : Mysql-driver for kexi

koffice-kexi-driver-pgsql.i386 : Postresql driver for kexi

libgda-mysql.i386 : MySQL provider for libgda

libgda-postgres.i386 : PostgreSQL provider for libgda

libgda-sqlite.i386 : SQLite provider for libgda

6. Showing a package's dependencies: yum deplist packagename will determine what pre-requisites are required to install that package, i.e. if I want to yum-install a package, what others will yum download and install first?

Code:
# yum deplist cacti

Loaded plugins: refresh-packagekit

Finding dependencies:

package: cacti.noarch 0.8.7b-4.fc10

 dependency: net-snmp

  provider: net-snmp.i386 1:5.4.2-3.fc10

  provider: net-snmp.i386 1:5.4.2.1-2.fc10

 dependency: php-snmp

  provider: php-snmp.i386 5.2.6-5

 dependency: /sbin/service

  provider: initscripts.i386 8.86-1

 dependency: mysql

  provider: mysql.i386 5.0.67-2.fc10

In this case, installing cacti requires net-snmp, php-snmp and mysql (amongst other packages), as well as the "service" executable, which is provided by installing the initscripts package.

7. Finding which package provides a particular command or file: yum provides filename - this is similar to the "search" option mentioned earlier, except it looks for the actual files within the package rather than search against package names themselves, for instance:

Code:
# yum provides "*lokkit"

Loaded plugins: refresh-packagekit

setuptool-1.19.4-2.fc9.i386 : A text mode system configuration tool

Repo        : fedora

Matched from:

Filename    : /etc/setuptool.d/99lokkit

system-config-firewall-tui-1.2.13-2.fc10.noarch : A text interface for basic

                                               : firewall setup

Repo        : fedora

Matched from:

Filename    : /usr/sbin/lokkit

Other       : lokkit = 1.7.0

In this case, two packages contain files matching the "lokkit" name - I can pick which package I require, depending upon which file/command I need.

8. Uninstalling package: yum erase packagename will attempt to erase a package, showing which other files (dependencies on this package) need to also be removed to prevent orphaned packages.

Code:
# yum erase httpd

Loaded plugins: fastestmirror, priorities

Setting up Remove Process

Resolving Dependencies

--> Running transaction check

---> Package httpd.i386 0:2.2.3-31.el5.centos set to be erased

--> Processing Dependency: httpd-mmn = 20051115 for package: mod_ssl

--> Processing Dependency: httpd-mmn = 20051115 for package: mod_perl

--> Processing Dependency: httpd-mmn = 20051115 for package: mod_python

--> Processing Dependency: httpd-mmn = 20051115 for package: php

--> Processing Dependency: webserver for package: webalizer

--> Processing Dependency: httpd = 2.2.3-31.el5.centos for package: mod_ssl

--> Processing Dependency: httpd for package: system-config-httpd

--> Processing Dependency: httpd = 2.2.3-31.el5.centos for package: httpd-manual

--> Processing Dependency: httpd >= 2.0.40 for package: mod_python

--> Processing Dependency: httpd for package: squirrelmail

--> Processing Dependency: httpd for package: squirrelmail

--> Running transaction check

---> Package httpd-manual.i386 0:2.2.3-31.el5.centos set to be erased

---> Package mod_perl.i386 0:2.0.4-6.el5 set to be erased

---> Package mod_python.i386 0:3.2.8-3.1 set to be erased

...

In this case, Apache modules that depend on HTTPD installed will also be removed when attempting to remove Apache web server.

For more information, use man yum.

3. YUM File Locations

1. Config Files:

There are several config files for YUM, the main one being /etc/yum.conf which used to contain not only directives affecting YUM's behaviour, but addresses directing YUM to FTP servers.

The latter are now located in a /etc/yum/repos.d/ directory, one .repo file per FTP site. On a default install there will probably be the official RedHat repos provided - you may need to manually add additional repos in order to access a wider range of software.

To get a quick report on what repos are configured, use yum repolist all:

Code:
# yum repolist all

Loaded plugins: refresh-packagekit

repo id              repo name                              status

adobe-linux-i386     Adobe Systems Incorporated             enabled:     17

fedora               Fedora 10 - i386                       enabled: 11,416

fedora-debuginfo     Fedora 10 - i386 - Debug               disabled

fedora-source        Fedora 10 - Source                     disabled

fusion               Compiz Fusion repository               enabled:     48

fusion-source        Compiz Fusion repository - source      disabled

fusion-testing       Compiz Fusion repository -testing      disabled

rawhide              Fedora - Rawhide - Developmental packa disabled

rawhide-debuginfo    Fedora - Rawhide - Debug               disabled

rawhide-source       Fedora - Rawhide - Source              disabled

updates              Fedora 10 - i386 - Updates             enabled:  3,104

updates-debuginfo    Fedora 10 - i386 - Updates - Debug     disabled

updates-source       Fedora 10 - Updates Source             disabled

updates-testing      Fedora 10 - i386 - Test Updates        disabled

repolist: 14,585

Use yum repolist enabled (or just yum repolist) to show only those in effect (enabled).

2. Cache Directories:

YUM usually downloads RPM files somewhere under the /var/cache/yum/ directory containing cache subdirectories per repo, holding RPM files and repo metadata. Usually you won't need to worry about this area - but if something goes wrong mid-yum it can be worthwhile dropping into those directories and manually (using rpm) installing some of the packages that have been downloaded, rather than re-download the entire lot again.

To clean out any cached files, use yum clean packages

3. Other Considerations

outdated header files: since YUM caches repo headers locally, these files could contain incorrect information. Use yum clean headers to flush this information out first.
flushing caches: if yum STILL seems to be ignoring config files and insists on using older information, use yum clean all to purge yum of cached packages, headers etc - then try again.
automatic package updates: the yum-updatesd service (yum-updates-daemon) can keep packages automatically updated - checking, downloading and installing without any manual intervention, rather like Windows Updates. However, some problems may be encountered on production servers with unchecked newer software being upgraded without any testing or evaluation, breaking an already-running system (dovecot - I'm looking at YOU!). For that reason, many admins prefer to set their updates to "notify" rather than automatically upgrade: check the /etc/yum/yum-updatesd.conf file for details on modifying yum-updatesd behaviour

Software Install with RPM

Sun, 26 Oct 2008 16:17:29 +0100

(based upon posts originally written by anyweb, kZo, Oroshi, grep420)

1. Overview

RedHat invented the RedHat Package Management system to ease installation and maintanence of software. Although you can still download raw source code and manually compile applications yourself, using a package management system like RPM provides a number of advantage:

no compiling: someone else has already done all the hard work of compiling, which saves you the hassle of getting a compiler and various libraries (Shared Objects)
package pre-requisites: the RPM package contains information about dependencies, so won't install if the pre-requisite files are missing or too old
package configuration: the RPM package usually contains some default/example config files - helps setting up the package from new
installation locations: paths in the RPM package conform to the standard Linux filesystem hierarchy (/usr/bin for binaries, /etc for config files, /var/log for logfiles, etc)
the RPM database: details of RPM-installed software are stored in an RPM database that can be interrogated to list all installed software, what files the package contains, etc.

2. Basic Commands

1. Listing installed packages: rpm -qa, for example:

Code:
$ rpm -qa | more

basesystem-8.0-5

ethtool-3-1

mktemp-1.5-23

perl-Filter-1.30-7

tcl-8.4.9-3

ed-0.2-38

MAKEDEV-3.19-1

pyxf86config-0.3.19-4

...

2. Showing information about a package: rpm -qi packagename (note that the package name, and not version needed to be specified), for example:

Code:
$ rpm -qi ethtool

Name        : ethtool                     Relocations: (not relocatable)

Version  : 3                                 Vendor: Red Hat, Inc.

Release  : 1                             Build Date: Thu 03 Mar 2005 11:08:26 PM GMT

Install Date: Wed 19 May 2004 01:16:31 AM BST     Build Host: tweety.build.redhat.com

Group      : Applications/System           Source RPM: ethtool-3-1.src.rpm

Size        : 134623                           License: GPL

Signature   : DSA/SHA1, Fri 20 May 2005 08:35:08 PM BST, Key ID b44269d04f2a6fd2

Packager    : Red Hat, Inc. 

URL      : http://sourceforge.net/projects/gkernel/

Summary  : Ethernet settings tool for PCI ethernet cards

Description :

This utility allows querying and changing of ethernet card settings,

such as speed, port, auto-negotiation, and PCI locations.

3. Listing package contents: rpm -ql packagename (again, only name and not version number needs to be given), for example:

Code:
$ rpm -ql bzip2

/usr/bin/bunzip2

/usr/bin/bzcat

/usr/bin/bzcmp

/usr/bin/bzdiff

/usr/bin/bzgrep

/usr/bin/bzip2

/usr/bin/bzip2recover

/usr/bin/bzless

/usr/bin/bzmore

4. Listing which package a file belongs to: rpm -qf /path/to/file - in this case, the absolute path to a filename must be specified. I have used the which command to determine the path in this case:

Code:
$ which nmap

/usr/bin/nmap

$ rpm -qf /usr/bin/nmap

nmap-4.53-1.0.cf.fc4

5. Listing contents of an uninstalled package: rpm -qlp /path/to/thisPackageHere.rpm - to see the contents of a package not yet installed, use the qlp options on the RPM file itself, eg:

Code:
$ rpm -qlp openssl096b-0.9.6b-6.i386.rpm

/lib/libcrypto.so.0.9.6b

/lib/libssl.so.0.9.6b

/usr/share/doc/openssl096b-0.9.6b

/usr/share/doc/openssl096b-0.9.6b/CHANGES

/usr/share/doc/openssl096b-0.9.6b/FAQ

6. Installing a package: rpm -ivh /path/to/thisPackage.rpm. i=install, v=verbose, h=hash signs to show progress, eg:

Code:
# rpm -ivh Bastille-3.0.9-1.0.noarch.rpm

Preparing...                ########################################### [100%]

  1:Bastille               ########################################### [100%]

#

Note that root privileges or equivilent (such as sudo) are needed to install RPM packages.

7. Upgrading a package: similar to above but uses the -U option rather than -i, i.e.: rpm -Uvh /path/to/thisPackage.rpm.

8. Checking packages: rpm -V packagename. Should be silent if there are no problems.

9. Checking ALL packages: rpm -Va. Make take some time, so run this command at quiet times, but a good command to run on a regular basis for a sanity check.

10. Uninstalling package: rpm -e packagename (erase package). If other (installed) packages are dependent upon this package, RPM will refuse to erase it, citing dependency issues.

For more information, use man rpm.

3. Other Considerations

Upgrade over install: it is possible to "upgrade" a package that doesn't exist, so many people stick to using the -Uvh rather than -ivh options when installing.
erasing leaves detritus: uninstalling a package usually leaves behind data files (logs, etc) as well as config files, which may need to be manually cleared out. On the other hand, don't assume that erasing will leave behind modified config files - make a backup first if you wish to preserve them!
finding RPMs: there are many RPM download sites out there - try www.rpmfind.net for a good start, google for others. Some sites dedicated to the development of specific applications often have pre-build RPMs on their download pages for fast install - search around.
distro-specific RPMs: Some RPMs are suited to specific distros, for example those that end in .fc7.rpm are for Fedora7, those ending in .mdk.rpm are from Mandrake Cooker (for Mandrake/Mandriva).
"noarch" RPMs: some RPMs ending in .noarch.rpm are not distro-specific and can be installed on any Linux distro, kernel version permitting. Webmin is a good example.
SRPMs: some RPMs with src in the filename are the source code, not compiled binaries. Installing these will only extract and copy the source code to development areas, not provide you with the actual binaries or applications - ensure you get the right file!
dependency hell: occasionally an RPM will require some pre-requisite packages, which themselves require other pre-requisites... you'll need to search around for those, or use something like yum (described elsewhere).
module/library dependency: occasionally RPM will complain about dependency upon a missing package, but a quick rpm -qa shows it is there. Look at installing packagename-devel, which contains library functions not essential to the normal operation of the package but others that depend upon it. It won't affect your original package, but should satisfy the dependency requirements.
compiled packages: it is still possible to download and compile packages outside of RPM but since they won't be included in the RPM database, RPM won't know they exist - and may still complain about missing dependencies.

how to create an rpm in mandriva

Thu, 18 Oct 2007 09:49:16 +0200

Hi,

I am newbie here, I wanto to know how to create an rpm in mandriva,

Thanks in adv.

I need help...

Sat, 24 Jun 2006 20:18:26 +0200

I tried installing ndiswrapper-1.18 with Konsole (SUSE 10.0) and I get this:

-----------------------------------------------------------------------------------------------------------------------------

linux:/home/juergen/ndiswrapper-1.18 # make install

make -C driver install

make[1]: Entering directory `/home/juergen/ndiswrapper-1.18/driver'

Can't find kernel build files in /lib/modules/2.6.13-15-default/build;

give the path to kernel build directory with

KBUILD= argument to make

make[1]: *** [prereq_check] Error 1

make[1]: Leaving directory `/home/juergen/ndiswrapper-1.18/driver'

make: *** [install] Error 2

------------------------------------------------------------------------------------------------------------------------------

Also when I try to install VMware I get the message that gcc and gcc+ not configured. Where can I install or download gcc and gcc+

Here is what it says:

-------------------------------------------------------------------------------------------------------------------------------

linux:/home/juergen # rpm -qa kernel* gcc* make

kernel-default-nongpl-2.6.13-15

kernel-update-tool-0.9-10

make-3.80-188

kernel-default-2.6.13-15

linux:/home/juergen #

----------------------------------------------------------------------------------------------------------------------------------

Where can I get kernel-source, gcc, and gcc-c++ packages.

Can anyon help with installing RPMs?

Sat, 10 Jun 2006 09:05:52 +0200

When I double click an RPM it says it's installing but then I don't see it anywhere to run it from. I have read that putting all of the RPMs in a folder then setting this as a folder of packages in yast can let me install them using yast but it won't let me do this- can anyone help please?

Cheers

Adam

rpm question, src or fc2 ??

Tue, 15 Feb 2005 15:43:44 +0100

I hope somebody can help clarify a point.

When looking at a site such as rpmfind I often see a list of rpm's that are for different versions e.g FC2, FC3 etc etc etc. You often see a .src.rpm file as well which, correct me if I am wrong, is the source code, but in a rpm package.

Does this mean that if I download this .src.rpm package and install that with...

rpm -ivh whatever.src.rpm it will install OK ???

I hope somebody can clear this up in my foggy mind.

Best wishes,

David.

dependancy hell

Fri, 24 Dec 2004 14:57:02 +0100

Computer - Dual 700, 5 SCSI HD Raid Array, Red Hat 9

Problem - Openldap-2.2.17 is currently installed. When this was installed, it broke 5 dependancies:

The following packages have unmet dependencies:

autofs: Depends: liblber.so.2

Depends: libldap.so.2

gnupg: Depends: libldap.so.2

libuser: Depends: liblber.so.2

Depends: libldap.so.2

nss_ldap: Depends: liblber.so.2

Depends: libldap.so.2

sendmail: Depends: liblber.so.2

Depends: libldap.so.2

I get the above message when I try to install ANYTHING with rpm or apt. I've tried to manually add libldap.so.2 (linked to libldap.so that I built manually from an old openldap which I did not install). Anyway, that didn't take.

So, I can't install anything with a package manager. I can't remove the new openldap because there are 33 packages with dependancies on the new libldap libraries including apache. It's hosting 5 live websites right now so it can't go offline.

Any ideas? I'm on the IRC channel as well if anyone can offer help.

Thanks,

Blake

Loads of RPMS!!!

Thu, 25 Mar 2004 17:06:52 +0100

Want to have access to almost all apps you can think of that are rpms and can easily be installed via apt-get? I know i do. This is like redhat's version of portage in a way. Its community supported in a way.

Just edit your /etc/apt/sources.list and add the following line in for whatever distro you use

Code:
Fedora core 2

rpm http://apt.physik.fu-berlin.de fedora/2/en/i386 at-testing

Fedora core 1

rpm http://apt.physik.fu-berlin.de fedora/1/en/i386 at-testing

RH 9

rpm http://apt.physik.fu-berlin.de redhat/9/en/i386 at-testing

then run

Code:
apt-get update && apt-get dist-upgrade

that will prompt you to upgrade some of the packages probably. Just type Y to continue

Once you are fully upgraded run

Code:
apt-get update

once more. You'll now notice you have a bunch more apt sources to find stuff in

if you run into this error on the apt-get update

Code:
rpmdb: unable to join the environment

error: db4 error(11) from dbenv->open: Resource temporarily unavailable

error: cannot open Packages index using db3 - Resource temporarily unavailable (11)

error: cannot open Packages database in 

E: could not open RPM database

don't worry.. just run the following commands to fix your rpm DB. Sometimes doing mass upgrades will cause RPM to confuse itself or error out. Repairing it fixes it 99% of the time

Code:
rm -rf /var/lib/rpm/__db.00*

rpm -vv --rebuilddb

apt-get update

another one from the J to the Y

extract 1 file from RPM

Wed, 14 Jan 2004 20:04:33 +0100

Do you want to extract a file from an rpm package, but don't want to install the whole rpm to get it? Well here is how you do it. I am going to grab htpasswd from the httpd rpm

To find out where the file will get installed if you install the whole package run this command

Code:
rpm -qlp httpd-2.0.40-21.i386.rpm | grep htpasswd

Now that i have /usr/bin/htpasswd as the location I can use rpm2cpio to grab just that file.

Code:
rpm2cpio httpd-2.0.40-21.i386.rpm | cpio -ivd ./usr/bin/htpasswd

That should place a file in ./usr/bin/htpasswd Notice I have a . (period) in front. It will create the usr/bin and then place htpasswd in that dir in whatever dir you are in. So in my example i was in /tmp so all the full path to htpasswd is

/tmp/usr/bin/htpasswd

From there i could move it to /usr/bin and delete /tmp/usr and also the rpm.

another one from J to the Y

How to build rpms

Wed, 07 Jan 2004 20:18:24 +0100

If you happen to find something you need but is not in rpm, the easy way is to use checkinstall to build one.

Get the checkinstall binary here: [/url][url=http://freshmeat.net/projects/checkinstall...C41%2C147%2C257]http://freshmeat.net/projects/checkinstall...C41%2C147%2C257

The only trick to using checkinstall is you replace make install with it.

example using fluxbox:

untar and gunzip the file

[jsw34@shadow sources]$ tar -xvzf fluxbox-0.1.14.tar.gz

cd into source dir

[jsw34@shadow sources]$ cd fluxbox-0.1.14

configure; make; and run checkinstall

[jsw34@shadow sources]$ ./configure && make && checkinstall

The package documentation directory ./doc-pak does not exist.

Should I create a default set of package docs? [y]:

Please choose the packaging method you want to use.

Slackware , RPM [R] or Debian [D]? R

Please write a description for the package.

End your description with an empty line or EOF.

>> My rpm

>>

you can edit the build values on the next screen or just hit ENTER to continue with the defaults.

Now it will build the rpm and install it.

Done. The new package has been installed and saved to

/usr/src/redhat/RPMS/i386/fluxbox-0.1.14-1.i386.rpm

voila!

If you have to use source, I highly reccommend using this tool. You will have accountability for everything you install and its really simple to remove or upgrade the package.

The rpms you build will be for the architecture you are using, however you can usually use them on newer releases, It may ask you for some newer dependencies though.

How to install an RPM

Mon, 15 Dec 2003 17:31:35 +0100

To install:

[v702623@snappy]# rpm -ivh foo.rpm

To update:

[v702623@snappy]# rpm -Uvh foo.rpm