[Spacewalk-list] spacewalk cobbler issue

[Jeremy Mueller]

Sorry for the confusion on this.  It looks like I was too hasty in
sending my original email.  I should've said that we use a custom %post
script to handle the rhn_register.  At the top of that we use sed to
disable all CentOS repos.  

We do manage repo files in the configuration management.  But we needed
a way to quickly disable all off-site repositories during the kickstart
process, and before the rhn_register was run, thus we used sed.

--Jeremy

-----Original Message-----
From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Kennedy, Ryan
Sent: Friday, February 26, 2010 11:18 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] spacewalk cobbler issue

I am probably missing something here so chime in if I am. But, why not
just have centrally managed /etc/yum.repos.d/CentOS-* files in the
configuration channel and those pushed to the clients.  Add the
spacewalk.repo file while you're at it.

I can see multiple pitfalls with using the sed one-liner to disable
those repos anyway.  Simple? yes.  Clean and robust? No.

-----Original Message-----
From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of John Hodrien
Sent: Friday, February 26, 2010 12:49 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] spacewalk cobbler issue

On Thu, 25 Feb 2010, Jeremy Mueller wrote:

> We had the same problem with a proxy and the CentOS mirrors.  At the
beginning of our %post section we put in this sed statement:
>
> sed -i 's/^\[\([^]]*\)\]/[\1]\nenabled=0/g' /etc/yum.repos.d/CentOS-*

I thought putting it in a post didn't work because the rhnreg happened
first,
so any packages installed via the activation key caused problems at that
stage.

I also (still) think disabling them that way is just setting yourself up
for
problems later.  Next time you upgrade centos-release, are you not
setting
yourself up for another sed?  Or does rpmnew save you?

jh