<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1>Hi Franky!<o:p></o:p>I’d be grateful if you could add that feature. Thank you very much.<o:p></o:p><o:p> </o:p>Regarding my setup, I have been trying to determine on my own what would be the best channel setup for my needs.<o:p></o:p>If anyone has a better layout/setup/examples/recommendations, I’d gladly have a look at it.<o:p></o:p><o:p> </o:p>I have assumed that a host can only access channels that are children of the parent that the host is subscribed to, is that assumption wrong?<o:p></o:p>I have also assumed that a host can only subscribe to one base channel aka the parent channel according to the assumption above. Wrong thinking?<o:p></o:p><o:p> </o:p>Regarding the split of channels based on purpose, that’s another assumption I have made since Red Hat Network has this channel layout, that the packages differ between the client/workstation/server/etc releases and that it would be wisest to mimic their setup.<o:p></o:p><o:p> </o:p>Maybe I have been “assuming” a little too much?<o:p></o:p><o:p> </o:p>Best regards<o:p></o:p><o:p> </o:p>Frank Mikkelsen Blohmé<o:p></o:p>Axis Communications AB<o:p></o:p><o:p> </o:p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>From: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] On Behalf Of Franky Van Liedekerke Sent: den 26 mars 2013 14:14 To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Cloning/syncing errata between channels<o:p></o:p></div></div><o:p> </o:p>On 2013-03-26 10:51, Frank Mikkelsen Blohmé wrote:<o:p></o:p><blockquote style='border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt'><div>Hi!<o:p></o:p>I’ve been trying to figure out how to clone/sync the errata in one channel into another channel within the same Spacewalk server (version 1.8) but haven’t found any resolution.<o:p></o:p><snip><o:p></o:p></div><div> <o:p></o:p></div><div>Sync the errata info from Fedora EPEL 5 and 6 errata files into Spacewalk channels using ya-errata-import.pl – Works for one channel with Fedora EPEL 5 RPMs and one channel with Fedora EPEL 6 RPMs. <o:p></o:p>9. <o:p></o:p></div><div> <o:p></o:p></div></blockquote><div> ya-errata-import.pl will import your errata into a channel if the packages for that errata are there.<o:p></o:p></div><div>Re-running ya-errata-import.pl with the same errata for another channel (for the same OS type) will indeed fail, just because like you said: the ID exists.<o:p></o:p></div><div> <o:p></o:p></div><div>Your setup is a bit unique in that way that you have the same OS type but for different purposes (workstation, server).<o:p></o:p></div><div>It's not difficult to add an option to add a suffix to errata, so I'll code it up.<o:p></o:p></div><div> <o:p></o:p></div><div>Franky<o:p></o:p></div></div></body></html>