Hi Spacewalkers,
anybody syncing SLES 12 SP3 Repos?
I am successfully syncing SLES 12 Repos since SLES 12 was released with the
method recently fabulous described by Bernd Helber (Hi Bernd!), but now I have
a weird Problem with SP3.
E.g. syncing of 2916 packages out of 3725 of the "OS Pool" re
quot;Repository URL" field in Spacewalk.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Lenhardt, Matthias
Gesendet: Donnerstag, 14. Dezember 2017 15:59
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Syncing SLES 12
: 'spacewalk-list@redhat.com'
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages
Hi Matthias,
I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the
3725 packages.
What I did was to first set up a SLES 12 SP3 VM and register it directl
Sent: Thursday, December 14, 2017 10:18 AM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages
Hi Matthias,
I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the
3725 packages.
What I did was t
2.6 on CentOS 7.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Daryl Rose
Gesendet: Donnerstag, 14. Dezember 2017 20:40
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages
Important hint:
Looking deaper into the error message. I found a possible error within the path
part of the download URL (Sorry, for not doing that earlier):
ERROR: Download failed:
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/x86_64/grep-2.16-3.1.x86_64.rpm
- [Errno 14] HTT
se
Gesendet: Donnerstag, 14. Dezember 2017 20:40
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Syncing SLES 12 SP3 Repos fails with some packages
Javier,
I'm also trying to setup a SLES 12 SP3 repo sync.
I also have a registered SLES 12 SP3 and I copied/pasted the "zypp
Important hint, part 2:
Solved the issue with the path myself by adding a slash between the repo URL
and the SuSE token:
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/?https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/?%3csuse-token>>
(Note the /
