Migrating patch repositories for Red Hat Enterprise Linux

The procedure described below generates an XML file that identifies the contents of the repository by its OS and architecture and provides the means for TrueSight Server Automation to consolidate all of the RPMs in a single location so that the repository can be used as a source for an offline patch catalog.

Use this procedure only in the following cases:

• The patch repository was initially created using TrueSight Server Automation Vendor Patch Content.
• You used a patch download utility that was not supplied by TrueSight Server Automation.
• You want to migrate a patch repository that was used in versions earlier than TrueSight Server Automation 7.0 to later versions of TrueSight Server Automation.

In this procedure, you define the location where that data is stored as well as the location where you want to create the payload source location used by TrueSight Server Automation.

• To create a payload source location for Red Hat Enterprise Linux
• Linux example

To create a payload source location for Red Hat Enterprise Linux

Enter the following command:

This command uses the following variables:

Linux example

The following example shows the command on a Linux machine:

Where:

• The source location is /opt/storage/patches/redhat/rhel-x86_64-server-5.
• The os-arch is RHES5-x86_64.

The following example demonstrates the use of the createRepo command on multiple directories:

In this example, the /repo/rhel5-all directory will contain RPMs from both the x86 and x86_64 channels and the offline catalog can be pointed at /repo/rhel5.