Using The Rhn Push Application - Red Hat NETWORK 3.7 - CHANNEL MANAGEMENTT GUIDE Manual

Chapter 6. Uploading and Maintaining Custom Packages
Option
--newest
--header
--source
--serverSERVER
--test
-h, --help
-?, --usage
Table 6-2.
rhnpush
Tip
These command line options are also described in the

6.2.2. Using the RHN Push application

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 package headers to the RHN Satellite Server and copies the packages
to the RHN Satellite Server package repository:
rhnpush -c label_of_private_channel pkg-list
Keep in mind, you can override the settings in your RHN Push configuration file(s) by specifying
options and values with the command, like so:
rhnpush -c label_of_private_channel --server localhost pkg-list
Description
server. Please note that source RPMs are special in that
their versions are never compared. Therefore, using this
option with RHN Push will upload source RPMs for the
specified channels only if they were not previously
uploaded, and binaries built from them exist in those
channels. In other words, you have to upload a binary
RPM before being able to use --newest with its source
RPM.
differently.)
Currently, a value of http://localhost/APP is necessary.
This parameter is required.
them.
options
Push only the packages that are newer than those on the
Upload only the headers.
Upload the indicated source packages. (We treat them
Specify the server to which packages will be uploaded.
Only print the packages to be pushed, don't actually push
Briefly describe the options.
View the usage summary.
rhnpush
man page:
man rhnpush
25
.