<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Have you looked at a python script called mergeErrata.py this uses the api to merge a security/bug or enhancement from a source channel into a cloned destination channel. Andy </div><div> On 16 Jun 2015, at 18:54, Waldirio Manhães Pinheiro <<a href="mailto:waldirio@gmail.com">waldirio@gmail.com</a>> wrote: </div><blockquote type="cite"><div>Hello Larry You can create a homolog channel frozen (copy from your original channel), clone your prod machine and subscribe in the new channel. Update accord your necessity and update/check your cloned system in the new homolog channel. If ok, you can say "yea the patch can be installed in my env and the app will work fine". After this you can apply the new patchs (tested in homolog channel) in the production / frozen channel. Let me know if was clear. Have a great day. <div class="gmail_quote">Em 16/06/2015 14:36, "Clegg, Larry E [HDS]" <<a href="mailto:Larry.Clegg@hdsupply.com">Larry.Clegg@hdsupply.com</a>> escreveu: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div lang="EN-US" link="#0563C1" vlink="#954F72"> <div> Greetings Spacewalkers, I have a process question for you. Here’s the setup: You have your systems setup in Spacewalk and subscribed to channels that are frozen in time, e.g. some systems are subscribed the channels with all the Q2 patches and updates. Other systems may still be subscribed to the Q1 patches and updates. You have your latest channels that are sync’d with the vendor’s latest offerings but no systems are subscribed to these “latest” channels. Let’s say a vendor (Redhat, Oracle, etc) releases a critical bug fix patch to their “latest” channel. Let’s say you want to deploy this critical bug fix asap – even though it is out of step with your quarterly patching cycle. You have a system that is subscribed to a channel tree that is frozen in time, for example a system is subscribed to your Q2 patches. You’re not ready to update everything yet but you do want this one critical bug fix patch (and any dependencies) to be made available to this system. How do you go about handling this type of situation? Thanks, Larry Larry Clegg HD Supply San Diego EMail: <a href="mailto:Larry.Clegg@HDSupply.com" target="_blank">Larry.Clegg@HDSupply.com</a> </div> </div> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote></div> </div></blockquote><blockquote type="cite"><div>_______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></div></blockquote></body></html>