On 14/05/18 02:13, jdow wrote: > I notice that the system which declares 7.3 has been supposedly running 7x for > a very long time now, before 7.4 went public. I also notice some of the > installed repos, such as elrepo, explicitly say 7x. Other's use $slreleasever. > > I figure there must be some good reason for this. I'm wondering what that good > reason might be.
$ rpm -q sl-release This should be a good indication. If this package is not updated, then the whole system announces itself as an older release - plus the base sl7-* repositories point at an older release as well. -- kind regards, David Sommerseth > On 20180512 06:15, Steven C Timm wrote: >> Two things could be happening-- >> >> (1) yum typically has a delay built into it of a couple days before it >> refreshes the repo cache when the repo has been changed, and thus may not >> have detected the new repo is there. >> (2) yum update could be failing for some reason--if you have a stock system >> there will be e-mail in your root account saying why. >> >> My systems got the 7.5 updates yesterday May 11. >> >> Steve Timm >> >> -------------------------------------------------------------------------------- >> >> *From:* [email protected] >> <[email protected]> on behalf of jdow >> <[email protected]> >> *Sent:* Saturday, May 12, 2018 4:29:35 AM >> *To:* scientific-linux-users >> *Subject:* Re: Why is 7.x still stuck at 7.4? >> On 20180511 21:26, jdow wrote: >>> I have yum-conf-sl7x.noarch installed. 7.5 seems to be out. But yum update >>> still >>> leaves the system declaring it is 7.4. >>> >>> {o.o} Joanne >>> >> At least that's what I get on one system. The other is still declaring 7.3: >> >> [... /etc]$ cat /etc/yum/vars/slreleasever >> 7.3 >> >> Shouldn't that read 7.x or something else if it's really following 7x? >> >> {^_^}
