The rhns-satellite-tools package provides the satellite-import program for managing all package, channel, and errata imports.
The following process assumes in the previous step the user has copied all data to /var/rhn-sat-import.
![]() |
Note |
---|---|
The trailing backslash (\) is a continuation character; it may safely be omitted. |
The first step in importing channels into the database is populating the tables describing common features for channels (channel families). This is accomplished by passing the --channelfamilies option to satellite-import:
satellite-import --channelfamilies --mountpoint /var/rhn-sat-import |
The next step creates a particular channel in the database and imports the metadata describing the channel:
satellite-import --channels -c redhat-linux-i386-8.0 \ --mountpoint /var/rhn-sat-import |
After running the preceding sample command, the user should see the redhat-linux-i386-8.0 channel data in the Web interface, although no package information will be present.
This second step parses the header metadata for each package in the channel, uploads the package data, and associates it with the channel.
satellite-import --packages -c redhat-linux-i386-8.0 \ --mountpoint /var/rhn-sat-import |
After running the preceding sample command, the user should be able to view package details in the redhat-linux-i386-8.0 channel from the Web interface. However, the actual packages will not yet be accessible.
![]() |
Note |
---|---|
Importing package data can take up to two hours per channel. |
The final step moves the RPM packages from the temporary repository into their final location.
satellite-import --rpms -c redhat-linux-i386-8.0 \ --mountpoint /var/rhn-sat-import |
After running the preceding sample command, the population of the channel should be complete. All of the packages should have been moved out of the repository; this can be verified with the command cd /var/rhn-sat-import/; ls -alR | grep rpm. If all RPMs have been installed and moved to their permanent locations, then this count will be zero, and the administrator may safely remove the temporary repository.