[Spacewalk-list] clone-by-date channel repositories

[Sean Barlow]

I'd like to create a clone-by-date-channel once a quarter so we can have
all machines updated to the same level.  I had previously done this in a
SUSE Manager server with another company fairly easy, but for CentOS I'm
running into some questions with each repo.  My spacewalk server is running
on CentOS 6.7 with Spacewalk 2.3 and is fully patched as of this time.

I have multiple clients that range from 6.2-6.7 but I want to update them
all to 6.7.
It appears that the 6.7 channel does not have all of the cumulative updates
for all packages.  Therefore do I need to include the vault repositories
that includes 6.0 base, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and the updated 6.7
repos so that I am sure I get all updates/dependencies?
For example:
Base 6 http://mirror.centos.org/centos/6/os/x86_64/

6.1 Updates http://vault.centos.org/6.1/updates/x86_64/

6.2 Updates http://vault.centos.org/6.2/updates/x86_64/

6.3 Updates http://vault.centos.org/6.3/updates/x86_64/

6.4 Updates http://vault.centos.org/6.4/updates/x86_64/

6.5 Updates http://vault.centos.org/6.5/updates/x86_64/

6.6 Updates http://vault.centos.org/6.6/updates/x86_64/

6.7 Updates http://mirror.centos.org/centos/6/updates/x86_64/

(I will also include extras/centosplus)

Or would the 6.7 and base 6 be sufficient for all clients 6.2-6.7?

--Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20151028/3ea9461a/attachment.htm>