[Spacewalk-list] "Whitelisting" certain RPMs

[Brian Collins]

The way I address this (with Satellite, not Spacewalk, but it works the same) is to make separate software channels (i.e. sandbox, beta, devel, production).  I move all new updates into sandbox.  Then I move them into beta and devel.  After we're satisfied with them, we put them in the production software channel.


> -----Original Message-----
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-
> bounces at redhat.com] On Behalf Of Paul Robert Marino
> Sent: Monday, August 12, 2013 4:51 PM
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] "Whitelisting" certain RPMs
> 
> An other alternative I've been considering is having two spacewalk servers
> one in a QA environment and a second in production. Then once my builds and
> updates pass QA testing using inter satellite sync to push the changes into
> production.
> 
> On Thu, Aug 8, 2013 at 8:05 AM, Dimitri Yioulos <dyioulos at onpointfc.com>
> wrote:
> > :-(
> >
> > Thanks, Michael.
> >
> >
> > On Thursday 08 August 2013 5:16:36 am Michael Mraka wrote:
> >> Dimitri Yioulos wrote:
> >> % Good morning (at least where I am), list.
> >> %
> >> % On some of my CentOS servers, there are certain packages %
> >> installed.  mainly as dependencies, for which, % unfortunately, there
> >> are seldom updates for them, or the % updates won't work with the
> >> main packages.
> >> Examples are % perl-Digest-SHA and libyaml.  So, when doing general %
> >> updates on those servers via yum, one would use % the --exclude
> >> switch.  What I've done is whitelisted those % packages in yum.conf,
> >> so as to avoid having to use the % switch.  I hope I explained that
> >> clearly.
> >> %
> >> % Regarding Spacewalk, is it possible to also whitelist those %
> >> packages so that under System Overview, the affected % systems don't
> >> show as needing to update the packages?
> >>
> >> Hi Dimitri,
> >>
> >> Nope, there's no way to simply suppress reporting this packages in
> >> webUI.
> >>
> >> The complex solution to this could be cloning the channel without
> >> excluded packages and subscribing clients to the cloned channel.
> >>
> >> Regards,
> >>
> >> --
> >> Michael Mráka
> >> Satellite Engineering, Red Hat
> >>
> >> _______________________________________________
> >> 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.
> >
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list