
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:
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_channelpkg-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 -c or --channel), the uploaded package headers are linked to all the
channels identified. If you do not specify a channel, the packages are deposited in the No
Channels section of the Package Management page. Refer to Section 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 -d option to 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 --stdin).
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 authentication), and the top
directory where packages live. This special configuration must not be edited and is located at
/etc/rhn/default/rhn_proxy_package_manager.conf. You can override the choices in that
default configuration file with settings in the main configuration file /etc/rhn/rhn.conf or via
command line options passed to RHN Package Manager.
Parameters not set in this file are read from .rhn_package_manager in the home directory of
the user currently logged in and finally from /etc/rhn/rhn_package_manager.conf. Make sure
all of these files have the appropriate permissions to prevent others from reading them.
Chapter 6. Uploading and Maintaining Custom Packages
26
Komentarze do niniejszej Instrukcji