If you had Repodata Depth as "2" and tried to push /games/poker.rpm, Nexus Repository would reject it. However, if you also had /games/poker.rpm, then you'd want to have Repodata Depth equal to "1," which would account for both the poker.rpm and the ashe.rpm in this example.
Nexus Repository will reject RPMs with less depth.įor example, if your package is created at /games/lol/ashe.rpm, then the Repodata Depth would be "2." When pushing the RPM, the metadata would be created at that level. This sets the level at which the repodata metadata folder will be created as well as the expected minimum folder depth at which the RPMs can exist in order to match. When creating a hosted Yum repository, you'll need to pick a Repodata Depth. Minimal configuration steps for creating a Yum Hosted repository are as follows: To host a Yum RPM, create a new yum (hosted) repository as documented in Repository Management. Hosting Yum RepositoriesĪ hosted repository for Yum can be used to upload both your own and third-party RPMs.
Also, see GPG signatures for Yum Proxy/Group for s igning data with a GPG key. See Proxying RHEL Yum Repositories for instructions on proxying Red Hat Enterprise Linux Yum repositories. You will need to determine which repositories are appropriate for your environment. Nexus Repository does not create a default Yum proxy repository.
0 kommentar(er)
