PDA

View Full Version : Howto config the default priority of repo while using SMT



meikestone
12-Feb-2013, 18:50
Hello,

when using a SMT-Server, how can I configure the default priority (of the repositories) which is used during the registration of the smt-client on SMT-Server?

Example:

smt-client ~# zypper lr -d

smt-client ~# wget http://smt-server/repo/tools/clientSetup4SMT.sh
smt-client ~# chmod 755 clientSetup4SMT.sh
smt-client ~# ./clientSetup4SMT.sh --host smt-server
.
.
.
-- here, the repositories are configured and refreshed --


smt-client ~# zypper lr -d


# | Alias | Name | Enabled | Refresh | Priority |
---+-----------------------------------------------------------+--------------------------------------------------+---------+---------+----------+-
1 | SMT-http_smt-server:SLES11-SP1-Pool | SLES11-SP1-Pool | Yes | Yes | 99 |
2 | SMT-http_smt-server:SLES11-SP1-Updates | SLES11-SP1-Updates | Yes | Yes | 99 |
3 | SMT-http_smt-server:SLES11-SP2-Core | SLES11-SP2-Core | Yes | Yes | 99 |
3 | SMT-http_smt-server:SLES11-SP2-Extension-Store | SLES11-SP2-Extension-Store | Yes | Yes | 99 |
5 | SMT-http_smt-server:SLES11-SP2-Updates | SLES11-SP2-Updates | Yes | Yes | 99 |
6 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | Yes | Yes | 99 |

Problem is, that all SLES repositories have the lowest possible priority! Thats bad, because if I add another repository what provide maybe equals packages as the SLES, the packages from this other repository will installed ... maybe ...
So in my opinion, the defaults for the SLES repositories should be higher, e.g. 50!

Thanks for help
Meike

malcolmlewis
12-Feb-2013, 22:29
On Tue 12 Feb 2013 05:54:01 PM CST, meikestone wrote:


Hello,

when using a SMT-Server, how can I configure the default priority (of
the repositories) which is used during the registration of the
smt-client on SMT-Server?

Example:

smt-client ~# zypper lr -d

smt-client ~# wget http://smt-server/repo/tools/clientSetup4SMT.sh
smt-client ~# chmod 755 clientSetup4SMT.sh
smt-client ~# ./clientSetup4SMT.sh --host smt-server
..
..
..
-- here, the repositories are configured and refreshed --


smt-client ~# zypper lr -d


Code:
--------------------
# | Alias |
Name | Enabled | Refresh |
Priority |
---+-----------------------------------------------------------+--------------------------------------------------+---------+---------+----------+-
1 | SMT-http_smt-server:SLES11-SP1-Pool |
SLES11-SP1-Pool | Yes | Yes
| 99 | 2 |
SMT-http_smt-server:SLES11-SP1-Updates |
SLES11-SP1-Updates | Yes | Yes
| 99 | 3 |
SMT-http_smt-server:SLES11-SP2-Core |
SLES11-SP2-Core | Yes | Yes
| 99 | 3 |
SMT-http_smt-server:SLES11-SP2-Extension-Store |
SLES11-SP2-Extension-Store | Yes | Yes
| 99 | 5 |
SMT-http_smt-server:SLES11-SP2-Updates |
SLES11-SP2-Updates | Yes | Yes
| 99 | 6 | SUSE-Linux-Enterprise-Server-11-SP2
11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2
11.2.2-1.234 | Yes | Yes | 99 | --------------------


Problem is, that all SLES repositories have the lowest possible
priority! Thats bad, because if I add another repository what provide
maybe equals packages as the SLES, the packages from this other
repository will installed ... maybe ...
So in my opinion, the defaults for the SLES repositories should be
higher, e.g. 50!

Thanks for help
Meike




Hi
No, only if you switch to it. Via zypper this would be via the --from
switch. Via YaST you need to either use the versions tab, or browse via
repository and press the 'switch' link.

--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 5 days 0:44, 4 users, load average: 0.13, 0.09, 0.07
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile

meikestone
13-Feb-2013, 00:01
No, only if you switch to it.

What do you mean with this?




Via zypper this would be via the --from
switch. Via YaST you need to either use the versions tab, or browse via
repository and press the 'switch' link.

I don't want manage the priority after registration for all the repositories. Imagine, you have 200 or more Servers and different repository on it ... manual management is prone to failure .. especially, if the setup for the servers are done from different peoples from different departments.

Is it not possible to define the default priority for a repository on SMT Server?

Thank you very much

Meike

meikestone
13-Feb-2013, 14:00
Problem is, that all SLES repositories have the lowest possible priority! Thats bad, because if I add another repository what provide maybe equals packages as the SLES, the packages from this other repository will installed ... maybe ...
So in my opinion, the defaults for the SLES repositories should be higher, e.g. 50!
Meike

Ok, I see now, that it has changed ... In newer installations of SLES11, the range of priority has changed to 1..200. Before, the range was only 0..99! So the default priority is o.k., I can add Repositories with lower priority than 99!

So the Problem is gone! Thanks for help

Meike