In Spacewalk you can only tie one RPM GPG key to a software channel, so syncing in RPM packages from various sources signed with different RPM GPG keys isn’t recommended. This can be circumvented by resigning all RPM packages with your own RPM GPG key before syncing them to Spacewalk. But then you will have to download the RPM packages somewhere before resigning them. This is why a 1:1 relationship is most convenient, one repo (one RPM GPG key) to one Spacewalk software channel. It’s easy to subscribe a host to a new channel in the GUI, can also be done on command line.
So if you have to add a new repo with RPM packages in the future: 1. Create a new software channel in Spacewalk, a child channel to the base channel to which the host is subscribed. 2. Configure the software channel using the repo’s RPM GPG key 3. Sync the RPMs in the repo into the software channel. 4. Subscribe the host to the new software channel 5. Install the RPMs on the host I hope this help you. Best regards Frank Mikkelsen Blohmé Axis Communications AB – IT Group Sweden, Lund Hi!, isn't it easier to subscribe a server to one channel and add in the future the needed repositories?, that way you don't have to touch that node in the future (hmm, maybe rhel nodes would need GPG Keys for package from a new repository :s) I'm trying to understand the channel/repo relationship to cover the most common use cases... Regards, -- Ciro Iriarte http://cyruspy.wordpress.com --
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
