[Spacewalk-list] FW: Updating software channel to new minor version
Jeremy Davis
jdavis4102 at gmail.com
Fri Aug 19 04:27:45 UTC 2011
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 <jtfalgout at gmail.com> wrote:
>
>
> On Thu, Aug 18, 2011 at 8:16 AM, Matt Moldvan <mmoldvan at dcctools.com> 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
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110818/e4334ee6/attachment.htm>
More information about the Spacewalk-list
mailing list