SCLO force yum to use 7.6.1810?

Issues related to applications and software problems
Post Reply
adrian.jackson
Posts: 3
Joined: 2019/09/19 17:56:35

SCLO force yum to use 7.6.1810?

Post by adrian.jackson » 2019/09/19 18:17:21

I'm not a regular CentOS user so please excuse me if this is a silly question.

Looking at the sclo for 7.6.1810 vs 7.7.1908 there have been a lot of packages removed e.g.

http://mirror.calgah.com/centos/7.6.181 ... x86_64/rh/
http://mirror.calgah.com/centos/7.7.190 ... x86_64/rh/

I thought that ... strange since I thought the point of the scl was to ensure long term stability but that's probably a misunderstanding on my part.

It seems that now when I run yum (with the scl enabled) it is pulling from the mirrors and accessing 7.7.1908 version and, in my case, since rh-ruby23 is missing, causing a few problems.

My question being ... is there anyway to force yum to use the 7.6.1910 repo? Tia :)

User avatar
TrevorH
Forum Moderator
Posts: 26590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: SCLO force yum to use 7.6.1810?

Post by TrevorH » 2019/09/19 18:46:34

You don't want to. All those packages were removed because they are EOL and no longer maintained. They will not receive security updates (or anything else) so are a potential danger.

See https://access.redhat.com/support/policy/updates/rhscl
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

adrian.jackson
Posts: 3
Joined: 2019/09/19 17:56:35

Re: SCLO force yum to use 7.6.1810?

Post by adrian.jackson » 2019/09/19 19:10:36

Sadly it's not a case of wanting to do this but one of needing to do so since this unexpectedly broke things and I'm looking for the simplest way to get something back up and running, hence the yum question.

As said though, I thought the point of CentOS was long term stability. Reading the page at https://wiki.centos.org/AdditionalResou ... tories/SCL it actually suggests that there is 10 years support. I'm just curious as to the discrepancy since Ruby 2.3 was released less than 4 years ago ...

Mike_Rochefort
Posts: 154
Joined: 2016/03/16 02:34:19

Re: SCLO force yum to use 7.6.1810?

Post by Mike_Rochefort » 2019/09/19 19:32:33

The point of CentOS is to provide a free, community run enterprise distribution which is accomplished by rebuilding RHEL. RHEL's purpose is the long term support that CentOS semi-inherits. CentOS only ever supports the latest releases RHEL packages, and those that are in current support. The SCL issue is something that was brought up in a past thread and was noted that the inclusion of packages that were no longer supported by Red Hat was a slip up, not meant to happen, and those packages would be culled.

Red Hat provides perpetual access to all versions of software released during a product's lifecycle without having to jump through hoops to get the RPMs for out-of-support-phase packages. To check the support status of an SCL package, view the following Red Hat page:

https://access.redhat.com/support/policy/updates/rhscl

Cheers,
Mike

User avatar
jlehtone
Posts: 2312
Joined: 2007/12/11 08:17:33
Location: Finland

Re: SCLO force yum to use 7.6.1810?

Post by jlehtone » 2019/09/19 19:46:38

adrian.jackson wrote:
2019/09/19 19:10:36
I thought the point of CentOS was long term stability. Reading the page at ...
That page has:
want both stability AND newer software.
CentOS for almost 10 years is the "stability". (There you have ruby-2.0 for "stability".)

Software Collections are the "newer software". At this point that seems to mean ruby-2.6. The SCL are short-lived.

fat-lobyte
Posts: 2
Joined: 2017/12/11 10:47:06

Re: SCLO force yum to use 7.6.1810?

Post by fat-lobyte » 2019/09/20 11:52:01

TrevorH wrote:
2019/09/19 18:46:34
You don't want to.
I for one, do want to. Due to limations of some dependencies, we need a specific GCC compiler version, namely GCC 6, and there is no way around that for now. If I could upgrade, I would.
TrevorH wrote:
2019/09/19 18:46:34
All those packages were removed because they are EOL and no longer maintained. They will not receive security updates (or anything else) so are a potential danger.
I don't understand the practice of removing EOL packages. There was no notice about it whatsoever, and Even Red Hat itself hasn't removed their old "unsupported" devtoolsets from their repositories.

What's worse is that it's not only uninstallable on 7.7 systems, but also on 7.6 systems. So even if I decide to not upgrade, I still cannot install what I used to be able to install.

I'm aware of the "potential danger", but I'd be willing to take the risk.

adrian.jackson
Posts: 3
Joined: 2019/09/19 17:56:35

Re: SCLO force yum to use 7.6.1810?

Post by adrian.jackson » 2019/09/23 14:58:54

Thanks for the insights all. As said, I am not au fait with centOS but had to get my hands dirty with this issue, so I appreciate insights on the longevity of the distribution and software collection.

That said, I see Ruby23 returned to http://mirror.calgah.com/centos/7.7.190 ... x86_64/rh/ and I'm curious if anyone can let me know what has happened here? Surely the removal of EOL packages should have at least have been announced _somewhere_ so that if this was a mistake users would know?

User avatar
TrevorH
Forum Moderator
Posts: 26590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: SCLO force yum to use 7.6.1810?

Post by TrevorH » 2019/09/23 15:08:13

It shouldn't have come back.
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply

Return to “CentOS 7 - Software Support”