I also found out that if I create another key for the same base channel it hasn't the Epel repository selected by default ( I can select it - it is not grey).

Kind regards,

Michiel

-------- Original Message --------
Subject: Re: [Spacewalk-list] 2 small questions
From: Michiel van Es <[email protected]>
To: [email protected] <[email protected]>
Date: 01/08/2010 02:08 PM

Hi Justin,

I did not set a universal key.
Only a centos 5 channel key.
When I look at child channels I see:

Any system registered using this activation key will be subscribed to
the selected child channels.

The following child channels of centos5 can be associated with this
activation key.

And then the epel_centos5 child channel selected.
Can I Unselect it?

On the old spacewalk server none of the child channels are selected but
on the new spacewalk server (0.7) the child channel is selected and so
all centos 5 clients get default the epel repo as child channel with
them. (which I dont't want)

Kind regards,

Michiel

-------- Original Message --------
Subject: Re: [Spacewalk-list] 2 small questions
From: Justin Sherrill<[email protected]>
To: [email protected]<[email protected]>
Date: 01/06/2010 09:01 PM

Michiel van Es wrote:
Hi I got 2 questions:

1)
I have a new spacewalk server where I have a main centos 5 i386 channel
and below the main channel a epel repo for centos 5.
Whenever I subscribe a node to the CentoS 5 main channel, it
automatically inherits it;s child : the epel repository.
How can I disable this feature or whay shoulde be done to let nodes only
subsribe to the main centos 5 channel but not it's child channels?


By default a system won't be auto-subscribed to the child channel.  Are
you sure you don't have the child channel specified in the activation
key you are registering with?

Also make sure you don't have an activation key set to be universal default.

2)
Is it possible to use yum priorities through spacewalk?
So you can say that the main channel packages always overrule the child
packages?
Or must this be done through the client's yum priorties package?

this doesn't currently work.  There is a bugzilla open on it though:

https://bugzilla.redhat.com/show_bug.cgi?id=515720

-Justin




_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to