Configuring And Using The Rhn Package Manager - Red Hat NETWORK 4.1.0 - CHANNEL MANAGEMENTT GUIDE Manual

26
custom packages cannot be downloaded through the RHN website, although they are
listed. They must be retrieved by the client system using
6.1.1. Configuring and Using the RHN Package Manager
Before you can use RHN Package Manager to upload packages into RHN, you need to first
manually copy the packages to the Proxy server itself. For example, from a development
host you can use
scp
scp foo.rpm root@rhnproxy.example.com:/tmp
When using RHN Package Manager to upload the packages into Red Hat Network, point
at the files you previously copied to the server.
Tip
Create at least one private channel to receive custom packages prior to upload into Red
Hat Network, 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 Server repository:
rhn_package_manager -c label_of_private_channel pkg-list
The label_of_private_channel is the custom channel created to receive these
packages. Be sure you use the precise channel label specified during its creation. If you
have one or more channels specified (using
headers are linked to all the channels identified. If you do not specify a channel, the pack-
ages are deposited in the No Channels section of the Package Management page. Re-
fer to Section 4.6 Assigning Packages to Software Channels for instructions on reassigning
packages.
The pkg-list reference represents the list of packages to be uploaded. These packages
must already be physically copied to the Proxy host. Alternatively, use the
specify the local directory that contains the packages to be added to the channel. RHN
Package Manager can also read the list of packages from standard input (using
Other options are specified in a configuration file, such as the Red Hat Network Server
URL, the HTTP proxy username and password (if your HTTP proxy requires authenti-
cation), and the top directory where packages live. This special configuration must not
be edited and is located at
You can override the choices in that default configuration file with settings in the main con-
Chapter 6. Uploading and Maintaining Custom Packages
:
/etc/rhn/default/rhn_proxy_package_manager.conf
up2date
or
-c --channel
.
), the uploaded package
option to
-d
--stdin
).
.