Uploading And Maintaining Custom Packages; Uploading Packages To Rhn Proxy Server; Configuring And Using The Rhn Package Manager - Red Hat NETWORK 3.6 - CHANNEL MANAGEMENTT GUIDE Manual

Uploading and Maintaining Custom Packages

Depending upon which Red Hat Network service is used, there are two different mechanisms for
uploading packages to private channels.
Customers of the RHN Proxy Server will use the RHN Package Manager application, which sends
package header information to the central Red Hat Network Servers and places the package itself into
the local repository of the RHN Proxy Server from which RHN Package Manager is invoked.
Customers of the RHN Satellite Server will use the RHN Push application, which sends package
header information to the local RHN Satellite Server and places the package into the local repository
of the RHN Satellite Server from which RHN Push is invoked.
This chapter discusses both of these tools in detail.
Warning
Remember, customers using both RHN Proxy Server and RHN Satellite Server should be using only
the RHN Push because this combination requires custom packages and channels be uploaded to the
Satellite only. From there, the Proxies will obtain the packages and distribute them to client systems.

6.1. Uploading Packages to RHN Proxy Server

The RHN Package Manager allows an organization to serve custom packages associated with a pri-
vate RHN channel through the RHN Proxy Server. If you want the RHN Proxy Server to update only
official Red Hat Enterprise Linux packages, you do not need to install the RHN Package Manager.
To use the RHN Package Manager, install the
and its dependencies. This package is available to registered RHN Proxy Server systems and may be
installed by running
Only the header information for the packages is uploaded to the RHN Servers. The headers are re-
quired so that RHN can resolve package dependencies for the client systems. The actual package files
( ) are stored on the RHN Proxy Server. For this reason, custom packages cannot be downloaded
*.rpm
through the RHN website, although they are listed. They must be retrieved by the client system using
.
up2date
6.1.1. Configuring and Using the RHN Package Manager
Note
It is recommended that at least one private channel be created to receive custom packages prior to
upload, since a channel is required for systems to obtain the packages.
The following command uploads the package headers to the RHN Servers and copies the packages to
the RHN Proxy Broker Server:
rhn_package_manager -c label_of_private_channel pkg-list
up2date rhns-proxy-package-manager
rhns-proxy-package-manager
.
Chapter 6.
RPM package