Earlier today I wrote: >On Tue, 16 Apr 2019 12:27:09 +0000, "Sadri, Wafa (BITBW)" <wafa.sa...@bitbw.bwl.de> wrote; >To: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com> >>Dear Paul-Andre, >> >>coincidentally I'm having a very similar issue. We fixed this issue in >>2.7 and it's now back because SW has fundamentally changed the way it >>syncs repos (either from 2.7 to 2.8 or 2.8 to 2.9 - not sure yet). >> >>best regards, >>Wafa
>Belated thanks. I had some issues with licenses that appeared to have expired on the SUSE site (even though we >had support), so I only got back to this recently when we found a solution to that issue. While I still need to set up >SUSE 12 for some servers, I'm also needing to set up SUSE 11 for SAP so I decided to look at the latter again. It >looks like some of the problems I was having must have been due to mistyped URLs. I did manage to get working >the two SLES 11 for SAP channels with which I was having problems, after re-creating the URLS - one with more >success than another. ... >Cheers, >Paul-Andre One more question, How are people out there configuring SLES 11 SP4 systems as Spacewalk 2.9 clients? https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients only seems to cover OpenSUSE, SLES 12 and SLES 15. Can you keep on using the Spacewalk 2.8 client for SLES 11 at http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2. 8/SLE_11_SP4/ with Spacewalk 2.9? Thanks, Paul-Andre _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
