CentOS - Nov 2020 - yum update security updates only

Frank,

Interesting thank you I didn't realize that.  It used to be supported I
believe, and there is a lot of out of date 3rd party documentation floating
around google that suggests it does.

Well it's just that many enterprises have policies which state that only
security updates should be installed, which I suspect is exactly why that
feature is no longer supported..

Eric


On Fri, Nov 13, 2020 at 3:55 PM Frank Cox <theatre at sasktel.net> wrote:
> On Fri, 13 Nov 2020 15:52:08 -0800
> Eric Chennells wrote:
>
> > Does anyone know what's going on here?
>
> That is unsupported by Centos.  So the short answer is, you can't do
that.
>
> Any particular reason you can't just update your system fully?
>
> --
> Can we uninstall 2020 and install it again? This one has a virus.
> MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

On Nov 13, 2020, at 19:01, Eric Chennells <eric.chennells at gmail.com>
wrote:
> 
> ?Frank,
> 
> Interesting thank you I didn't realize that.  It used to be supported I
> believe, and there is a lot of out of date 3rd party documentation floating
> around google that suggests it does.
> 
> Well it's just that many enterprises have policies which state that
only
> security updates should be installed, which I suspect is exactly why that
> feature is no longer supported..
I don?t believe CentOS has ever supported it in any of the supported releases,
although repos like EPEL do provide security metadata.

RHEL supports the security flag to yum update, because they curate their repo
metadata with that data, but it isn?t available to CentOS users.

--
Jonathan Billings <billings at negate.org>

On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells <eric.chennells at
gmail.com>
wrote:
> Frank,
>
> Interesting thank you I didn't realize that.  It used to be supported I
> believe, and there is a lot of out of date 3rd party documentation floating
> around google that suggests it does.
>
> Well it's just that many enterprises have policies which state that
only
> security updates should be installed, which I suspect is exactly why that
> feature is no longer supported..
>
There are ways to get the metadata to do that, but it's still not
officially supported. And as for enterprises mandating only security
updates, they would/should pay for RHEL to get that kind of feature.

We utilize Spacewalk and the errata from https://cefs.steve-meier.de/ to provide
this function for CentOS.

Andrea

-----Original Message-----
From: CentOS <centos-bounces at centos.org> On Behalf Of Jon Pruente
Sent: Friday, November 13, 2020 7:08 PM
To: CentOS mailing list <centos at centos.org>
Subject: {EXTERNAL} Re: [CentOS] yum update security updates only


CAUTION:??This email originated outside of BSWH; avoid action unless you know
the content is safe. Send suspicious emails as attachments to BadEmail at
BSWHealth.org.

On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells <eric.chennells at
gmail.com>
wrote:
> Frank,
>
> Interesting thank you I didn't realize that.  It used to be supported 
> I believe, and there is a lot of out of date 3rd party documentation 
> floating around google that suggests it does.
>
> Well it's just that many enterprises have policies which state that 
> only security updates should be installed, which I suspect is exactly 
> why that feature is no longer supported..
>
There are ways to get the metadata to do that, but it's still not officially
supported. And as for enterprises mandating only security updates, they
would/should pay for RHEL to get that kind of feature.
_______________________________________________
CentOS mailing list
CentOS at centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!XuXhHdKtZFfgqvwdbBq9PZb3K3TydTqyOHYfhFUGuM5eVBWP-eY3A7sFdZEJM8J5vg$

**********************************************************************
The information contained in this e-mail may be privileged and/or confidential,
and protected from disclosure, and no waiver of any attorney-client, work
product, or other privilege is intended.  If you are the intended recipient,
further disclosures are prohibited without proper authorization. If you are not
the intended recipient (or have received this e-mail in error) please notify the
sender immediately and destroy this e-mail. Any unauthorized copying, disclosure
or distribution of the material in this e-mail is strictly forbidden and
possibly a violation of federal or state law and regulations. The sender and
Baylor Scott & White Health, and its affiliated entities, hereby expressly
reserve all privileges and confidentiality that might otherwise be waived as a
result of an erroneous or misdirected e-mail transmission. No employee or agent
is authorized to conclude any binding agreement on behalf of Baylor Scott &
White Health, or any affiliated entity, by e-mail without express written
confirmation by the CEO, the Senior Vice President of Supply Chain Services or
other duly authorized representative of Baylor Scott & White Health.