MichaelBalack
asked on
Where to get the SuSE updated zypper repositories?
This is using SuSE Enterprise server 11 with Service Pack 4. Please see the configure zypper repositories for updates, patches as follows,
#zypper lr -u
Refreshing service 'spacewalk'.
# | Alias | Name | Enabled | Refresh | URI
---+---------------------- ---------- ---------- --------+- ---------- ---------- ---------- ---------- ---------+ ---------+ ---------+ ---------- ---------- ---------- ---------- ---------- ---------- ---------- -
1 | SUSE-Linux-Enterprise-Serv er-11-SP4_ 11.4.4-1.1 09 | SUSE-Linux-Enterprise-Serv er-11-SP4 11.4.4-1.109 | Yes | No | iso:///?iso=SLES-11-SP4-DV D-x86_64-G M-DVD1.iso &url=file: ///mnt/iso /
2 | samba_upd | samba_upd | Yes | No | dir:///kk
3 | spacewalk:sle11-hae-sp4-po ol-x86_64 | SLE11-HAE-SP4-Pool for x86_64 | Yes | Yes | plugin:spacewalk?channel=s le11-hae-s p4-pool-x8 6_64&serve r=0
4 | spacewalk:sle11-hae-sp4-up dates-2016 0920 | SLE11-HAE-SP4-Updates-2016 0920 | Yes | Yes | plugin:spacewalk?channel=s le11-hae-s p4-updates -20160920& server=0
5 | spacewalk:sle11-sdk-sp4-po ol-x86_64 | SLE11-SDK-SP4-Pool for x86_64 | No | Yes | plugin:spacewalk?channel=s le11-sdk-s p4-pool-x8 6_64&serve r=0
6 | spacewalk:sle11-sdk-sp4-up dates-2016 0920 | SLE11-SDK-SP4-Updates-2016 0920 | No | Yes | plugin:spacewalk?channel=s le11-sdk-s p4-updates -20160920& server=0
7 | spacewalk:sles11-sp4-impor tant-updat es | SLES11-SP4-Important-Updat es | Yes | Yes | plugin:spacewalk?channel=s les11-sp4- important- updates&se rver=0
8 | spacewalk:sles11-sp4-pool- x86_64 | SLES11-SP4-Pool for x86_64 | Yes | Yes | plugin:spacewalk?channel=s les11-sp4- pool-x86_6 4&server=0
9 | spacewalk:sles11-sp4-suse- manager-to ols-x86_64 | SLES11-SP4-SUSE-Manager-To ols x86_64 | Yes | Yes | plugin:spacewalk?channel=s les11-sp4- suse-manag er-tools-x 86_64&serv er=0
10 | spacewalk:sles11-sp4-updat es-2016092 0 | SLES11-SP4-Updates-2016092 0 | Yes | Yes | plugin:spacewalk?channel=s les11-sp4- updates-20 160920&ser ver=0
11 | spacewalk:sles11-sp4-packe r | Packer IT-GI-HS Repository SLES11 SP4 | Yes | Yes | plugin:spacewalk?channel=s les11-sp4- wacker&ser ver=0
Think all these repositories are "local", and those updates/patches provided are pretty outdated. For example, if I want to update the os kernel, and when I typed "zypper up kernel*", the answer given is "kernel-default version is already installed".
Can I point to any public-available suse repository? If so, any recommended URL?
Thanks
#zypper lr -u
Refreshing service 'spacewalk'.
# | Alias | Name | Enabled | Refresh | URI
---+----------------------
1 | SUSE-Linux-Enterprise-Serv
2 | samba_upd | samba_upd | Yes | No | dir:///kk
3 | spacewalk:sle11-hae-sp4-po
4 | spacewalk:sle11-hae-sp4-up
5 | spacewalk:sle11-sdk-sp4-po
6 | spacewalk:sle11-sdk-sp4-up
7 | spacewalk:sles11-sp4-impor
8 | spacewalk:sles11-sp4-pool-
9 | spacewalk:sles11-sp4-suse-
10 | spacewalk:sles11-sp4-updat
11 | spacewalk:sles11-sp4-packe
Think all these repositories are "local", and those updates/patches provided are pretty outdated. For example, if I want to update the os kernel, and when I typed "zypper up kernel*", the answer given is "kernel-default version is already installed".
Can I point to any public-available suse repository? If so, any recommended URL?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The OpenSUSE repos are standard and completely compatible with SLES. The main thing with SLES over OpenSUSE is the paid support.
ASKER
Hi David,
I know is a bit odd. However, these SuSE servers weren't setting up by me and my team.
I know is a bit odd. However, these SuSE servers weren't setting up by me and my team.
ASKER
Hi David,
Some more, the licenses weren't kept by us.
Some more, the licenses weren't kept by us.
ASKER
Thanks for Expert - serialband, in suggesting given links. It works
If you installed using normal SUSE installation steps, then the update repositories should have been setup by default.
You must be very careful specifying what you're calling public repositories. Sometimes non-SUSE standard repositories can create package conflicts which are very difficult to fix.
Best to stick with standard/default SUSE repositories, unless your an expert at recovering from packaging error problems.