Hello, Not directly. The method I use for SLES 12 and 15 is to sync the target repos to a local SMT server using smt-mirror, then use a scripted cron job to push these package updates to custom Spacewalk channels via rhnpush. It's not elegant but it works as a staging process with granular control over what updates go to specific channels for testing in dev before being pushed to prod.
From: [email protected] <[email protected]> On Behalf Of Alan Pittman Sent: Thursday, January 16, 2020 8:51 AM To: [email protected] Cc: Spencer Chan <[email protected]> Subject: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk [EXTERNAL EMAIL] Hi, Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare notes with you please? I have been successfully syncing SLES11 and SLES12 repos for some time now, but haven't been able to get a SLES 15 repo to sync. Suse support isn't any help. They will only verify the URL and userid/password. Any help would sure be appreciated. Alan Alan Pittman Publix Super Markets, Inc. [email protected]<mailto:[email protected]> 1-863-686-8754 x46320 Unix is user friendly. It's just very selective about who its friends are.
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
