On 6 July 2010 00:46, McLeod, Matt <[email protected]> wrote: > Tom Brown wrote: > > Problem is, cloning seems to be a one-time operation. Updates that go into > the source channel don't make it into the destination. > > > > As I see things cloning is a point in time snapshot of a channel and this is > how we use it. Updates channels are cloned monthly and tagged so that > machines can be provisioned to any of those points in time in the future. > > > > Sure, and I see the value of that, but how about when what you want is the > same child channel attached to multiple parents? It seems wasteful to be > syncing all updates twice. > > > > Matt > > > > ++++++++++++++++++++++++++++++++++++++++++++++++ > The information contained in this communication is strictly confidential and > intended solely for the use of the intended recipient(s). The copyright in > this communication belongs to ITG Australia Ltd, ITG Hong Kong Limited, ITG > Singapore Pte Ltd and/or their related entities, including Investment > Technology Group, Inc., (collectively referred to as “ITG") and may contain > information that is private, confidential or subject to legal professional > or other privilege. No confidentiality or privilege is waived or lost by any > mis-transmission of this email. > > Access to this email by anyone other than the intended recipient is > unauthorized and further distribution of this email is strictly prohibited > without the permission of ITG. If you are not the intended recipient of this > email, any review, disclosure, copying, distribution, retention or any > action taken or omitted to be taken in reliance on it is prohibited and may > be unlawful. If you are not the intended recipient of this email, you should > not disseminate, distribute or copy this e-mail and you should delete it and > all copies of it from your system, destroy any hard copies of it and notify > the sender. ITG and/or its affiliates reserve the right to monitor and > archive all electronic communications through its/their network. > > The information contained in this email is believed to be accurate at the > time of publication. However, ITG disclaims all responsibility for any loss > or damage howsoever arising as a result of any person or entity acting upon > the information contained in this email and no liability will be accepted by > ITG for any such loss or damage. Any views expressed in this email are those > of the individual sender, except where the email states otherwise and the > sender is authorized to state them to be the views of ITG. > ++++++++++++++++++++++++++++++++++++++++++++++++ > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
It would seem to me that putting together a simple script to run against the API would do the trick... After the sync to the upstream repo on the first EPEL channel have a script call the channel.software.mergePackages() function with the primary/clone channels as parameters as per the API docs... That would eliminate the multiple resposync upstream and should be much more bandwidth efficient... James _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
