<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> On -28163-01--10 20:59, Jet Wilda wrote: <blockquote cite="mid:%3C02EB42D2477149418837A74C416B819F158AC394@webmail.noam.fadv.com%3E" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta name="Generator" content="Microsoft Word 12 (filtered medium)"> <style>  </style>  <div class="WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> Please excuse my ignorance but I still do not understand something. I get how to populate the channels in the Spacewalk server. What I do not understand is how you prevent packages from EPEL or RpmForge from overwriting base OS packages on the workstation that pulls its updates (yum update) from the Spacewalk server. Does the fact that they are child channels automatically make it so they won’t step on the top base channel? </div> </blockquote> No, be a child channel don't prevent overwriting ... If you sync EPEL repository directly to Spacewalk server channel, you put all rpms in spacewalk, including those overwriting base OS packages. But, if you sync CentOS base, updates, extras and EPEL repositories with command 'reposync -l bla bla bla ' ('-l' flag = enable yum plugin support) to local directories, you don't download Epel rpms that could overwrite base OS packages, because you are using priority plugin ... Now, if you sync every local directories ( those with CentOS base, updates, extras and EPEL rpms downloaded above) to spacewalk channels, you don't upload rpms that could overwrite base OS packages, because you have never download them ... Marco <blockquote cite="mid:%3C02EB42D2477149418837A74C416B819F158AC394@webmail.noam.fadv.com%3E" type="cite"> <div class="WordSection1"> Thanks again for answering my questions and being so patient with me as I try to understand.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> ~Jet<o:p></o:p> <o:p> </o:p> <div> <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;"> From: <a class="moz-txt-link-abbreviated" href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [<a class="moz-txt-link-freetext" href="mailto:spacewalk-list-bounces@redhat.com">mailto:spacewalk-list-bounces@redhat.com</a>] On Behalf Of Marco Giunta Sent: Thursday, September 23, 2010 4:08 AM<o:p></o:p> </div> </div> <o:p> </o:p> On -28163-01--10 20:59, Jet Wilda wrote: <o:p></o:p> Hi,<o:p></o:p> <o:p></o:p> So then your workstations have the spacewalk server and your local yum repository setup to get RPMs from. Am I understanding that correctly?<o:p></o:p> No, my workstations have only spacewalk repository by rhnplugin <o:p></o:p> Or how do the work stations get something from say EPEL that isn’t setup via it’s activation key channels?<o:p></o:p> In my spacewalk server I have a channel for every different repository: Centos base, updates, extras, Epel, Rpmforge, Karan , Spacewalk-client and another with my personal rpms. Every night, a cron script, sync all repositories from external source with 'reposync -l bla bla bla ' ('-l' flag = enable yum plugin support) to a local directories on my spacewalk server; in this way I manage 'priority plugin'. Then, same script, sync my local mirrors with spacewalk channels (spacewalk-repo-sync bla bla bla) My activation keys have as base channel, CentOS Base and as child channels, all other channels. So, with 'yum install bla bla' I can install a rpm belong to Epel, from my spacewalk server ... Marco <o:p></o:p> <o:p></o:p> Thanks,<o:p></o:p> ~Jet<o:p></o:p> <o:p></o:p> <div> <div style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;"> From: <a moz-do-not-send="true" href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [<a moz-do-not-send="true" href="mailto:spacewalk-list-bounces@redhat.com">mailto:spacewalk-list-bounces@redhat.com</a>] On Behalf Of Marco Giunta Sent: Wednesday, September 22, 2010 2:41 AM<o:p></o:p> </div> </div> <o:p></o:p> Hi, workstations are connected to spacewalk server repository by 'rhnplugin'; I think you can enable or disable a channel modifing '/etc/yum/pluginconf.d/rhnplugin.conf': /etc/yum/pluginconf.d/rhnplugin.conf [main] enabled = 1 gpgcheck = 1 # You can specify options per channel, e.g.: # #[rhel-i386-server-5] #enabled = 1 # #[some-unsigned-custom-channel] #gpgcheck = 0 But you cannot manage priority, AFAIK. I manage it in this way: - first, I sync external repositories (centos update, extras, rpmforge, epel and karan) with 'reposync -l bla bla bla ' ('-l' flag = enable yum plugin support) to a local directories on my spacewalk server -then I sync my local mirrors with spacewalk channels (spacewalk-repo-sync bla bla bla) Marco On -28163-01--10 20:59, Jet Wilda wrote: <o:p></o:p> Hi,<o:p></o:p> <o:p></o:p> I’m trying to understand the relationship of the files in /etc/yum.repos.d/*.rep once a system is configured to sync against the spacewalk server. Are those files not used at all once the system is using spacewalk? If not is there a place that you can configure the repo settings like priority, enabled, etc?<o:p></o:p> <o:p></o:p> Thanks,<o:p></o:p> ~Jet<o:p></o:p> <o:p></o:p> <pre>-- <o:p></o:p></pre> <pre> -----------------------------------<o:p></o:p></pre> <pre>|Marco Giunta - SISSA Computer Staff|<o:p></o:p></pre> <pre>|Via Bonomea, 265 |<o:p></o:p></pre> <pre>|34136 - Trieste, Italy |<o:p></o:p></pre> <pre>|Tel: +39-40-3787-503 |<o:p></o:p></pre> <pre>|Fax: +39-040-3787-528 |<o:p></o:p></pre> <pre>|e-mail: giunta AT sissa.it |<o:p></o:p></pre> <pre> -----------------------------------<o:p></o:p></pre> <o:p></o:p> <pre>-- <o:p></o:p></pre> <pre> -----------------------------------<o:p></o:p></pre> <pre>|Marco Giunta - SISSA Computer Staff|<o:p></o:p></pre> <pre>|Via Bonomea, 265 |<o:p></o:p></pre> <pre>|34136 - Trieste, Italy |<o:p></o:p></pre> <pre>|Tel: +39-40-3787-503 |<o:p></o:p></pre> <pre>|Fax: +39-040-3787-528 |<o:p></o:p></pre> <pre>|e-mail: giunta AT sissa.it |<o:p></o:p></pre> <pre> -----------------------------------<o:p></o:p></pre> </div> </blockquote> <pre class="moz-signature" cols="72">-- ----------------------------------- |Marco Giunta - SISSA Computer Staff| |Via Bonomea, 265 | |34136 - Trieste, Italy | |Tel: +39-40-3787-503 | |Fax: +39-040-3787-528 | |e-mail: giunta AT sissa.it | -----------------------------------</pre> </body> </html>