I've been taking the exact same approach. I pretty much just mirror what the CentOS mirrors have - a current point release and then a child updates channel. In order to keep things clean, I also take the (probably unnecessary) step of cleaning out the base channel completely of packages before re-syncing from the CentOS base channel.
From: Jeremy Davis <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Fri, 19 Aug 2011 00:27:45 -0400 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Spacewalk-list] FW: Updating software channel to new minor version I am not sure on the Scientific Linux issue but in regards to minor releases (5.5,5.6 etc.) I use the same base channels. I have a base channel setup with the contents of the OS repo from centos. Then under the base I have updates which is a mirror of the updates repo. Centos has a major release repository that contains the latest release (4, 5, 6). Then they have the minor release directory that contains the minor release (4.9, 5.6, 6.0). I use the latest release for my repo sync(4, 5, 6). This has worked for upgrading Centos 5.2 all the way up to 5.6 using the same channels and repository. I just sync the new packages when added. No other changes are made and this can all be automated. This is because when Centos releases a new minor version they update the major release directory with the packages for the latest release. Now major releases get a new base channel (just like centos creates the new release directory). I hope this helps. If you have any questions please feel ! free to ask. Thanks, Jeremy On Aug 18, 2011, at 6:09 PM, Jeff Falgout <[email protected]<mailto:[email protected]>> wrote: On Thu, Aug 18, 2011 at 8:16 AM, Matt Moldvan <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: In response to Sascha: Our spacewalk server is now working quite well. Before rollout I tested the update of our Scientific Linux 6 channel from 6.0 to 6.1 (6.1 is called 6rolling, because it is not release yet). ________________________________ Has anyone found a good solution to this? I'm experiencing the same type of issue now, having installed Spacewalk on Scientific Linux 6, then running a yum update on the Spacewalk server which broke it's ability to update through Spacewalk. Do we really need to create new channels everytime a minor version is released? Is there a "best practices" document or resource somewhere for Spacewalk? How does the RH Satellite product address this same issue? Thanks, Matt. +1 on the problem .... No solution yet and I'm on 1.6 nightly for server .... 1.5 for clients _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
