[Spacewalk-list] Repo update question

[Dimitri Yioulos]

Thomas,

That's a fairly accurate description of what I've set up.  
The Sernet Samba channels are set to be updated on 
Saturdays via a schedule created in Spacewalk.

In a previous thread, another poster mentioned that I 
would "unfortunately ... have to "re-sync" [my] i386 cloned 
channel manually on webUI (Manage Software Channels > 
<channel> > Packages > Add) or you may atomate it via 
script / API calls".  In a moment of clarity, it dawns on 
me that this is a step I might have bypassed.  I'll know if 
that's the case next time there are Samba updates available 
from Sernet.

Sorry for the noise.  But, at least this gave me the 
opportunity to lay the whole thing out in front of me.

Dimitri


On Friday 16 August 2013 9:13:32 am Thomas Foster wrote:
> I want to understand your setup let me know if this is
> correct.
>
> You have a cloned channel that servers are subscribed to
> and that channel is updated on Saturday(manually or job
> created?) from sernet with Samba packages.  When a new
> package is added your servers do not see the package
> until you delete the previous package from the cloned
> channel, right?  When you delete the package you do not
> clear the cache and run yum update package and it can see
> the new package or do you run yum clean all then update?
>
> On Aug 15, 2013 10:52 AM, "Dimitri Yioulos" 
<dyioulos at onpointfc.com> wrote:
> > Hey, all.
> >
> > I'm continuing to tweak and/or try to bend Spacewalk to
> > my will.  This morning, I ran "yum update" on one of my
> > servers, and noticed that there was a Samba update
> > (from Sernet).  This wasn't reflected in the Samba
> > channels I created in Spacewalk, which is OK, since I
> > have these channels set to update every Saturday
> > afternoon, the first of which comes up this Saturday. 
> > But, to make sure everything works as it should, I
> > updated the channels manually from the CLI.  Worked
> > fine.
> >
> > Now, as per help through an earlier post, I created
> > cloned channels of the original Samba channels so as to
> > be rid of the x86_64 packages, which I don't use, and
> > which without being rid of would cause the updates to
> > my machines to fail.  Also works fine.
> >
> > BUT, I noticed after the manual update that my machines
> > weren't seeing the new Samba packages.  It was only
> > after I 1) deleted the previous version packages in the
> > original Samba channels, and 2) deleted the packages in
> > the cloned Samba channels, that my machines now saw
> > that updates were available.
> >
> > I understand from the previous post that I have to
> > accomplish 2) either manually or via a script.  My
> > question though (and sorry it's taken me so long to get
> > here) is should newly updated packages replace older
> > ones in my original Samba channels (or any channels,
> > for that matter), or must I go through this two-step
> > process each time an update occurs?
> >
> > Regards,
> >
> > Dimitri
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.