Migrating   patch repositories for   SUSE Linux Enterprise

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

Use this procedure 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.

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

To create a repository for SUSE Linux Enterprise

Enter the following command:

suse_downloader.sh -createRepo -srcLocation "<locationOperSysArch>"
-repoLocation "<repositoryPath>"
Example
suse_downloader.sh -createRepo -srcLocation "/Source_Location1,SLES9-x86;/Source_Location2;SLES9-x86_64" -repoLocation "/Repository_Location"

This command uses the following variables:

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

suse_downloader.sh -createRepo -srcLocation "/repo/SLES11_SP2x86,SLES11-x86;/repo/SLES11_SP2x64,SLES11-x86_64" -repoLocation  "/repo/SLES11_SP2-all"

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*