My system is 7.2.1511.
When I run "yum update", it wants to install about 900 packages total. Most are labeled just "el7". A few "el7_1" and a lot are "el7_3" or 7.3. None are 7.2.
I'm not surprised when I see 50-100 packages needing an update. But 900? And none specific to the installed system?
My last update, of 4 packages, was Dec 31, 2016. I first noted the current behavior about 10 days later and have been trying to figure out why such an unusual report.
Any suggestions?
Jon
On 01/26/2017 06:00 PM, Jon LaBadie wrote:
My system is 7.2.1511.
When I run "yum update", it wants to install about 900 packages total. Most are labeled just "el7". A few "el7_1" and a lot are "el7_3" or 7.3. None are 7.2.
I'm not surprised when I see 50-100 packages needing an update. But 900? And none specific to the installed system?
My last update, of 4 packages, was Dec 31, 2016. I first noted the current behavior about 10 days later and have been trying to figure out why such an unusual report.
CentOS 7 is the release .. point releases (7.0.1406, 7.1.1503, 7.2.1511, 7.3.1611), are 'point in time' snapshots of the CentOS 7 tree.
CentOS has no mechanism to stay on 7.2.1511 when 7.3.1611 has been released. 7.3 and 7.2 are really just CentOS-7 with updates.
The update you are seeing is the CentOS-7 tree after we finished releasing all the 7.3.1611 packages (and updates to 7.3.1611)
On 1/26/2017 4:00 PM, Jon LaBadie wrote:
My system is 7.2.1511.
When I run "yum update", it wants to install about 900 packages total. Most are labeled just "el7". A few "el7_1" and a lot are "el7_3" or 7.3. None are 7.2.
I'm not surprised when I see 50-100 packages needing an update. But 900? And none specific to the installed system?
yum update of any centos 7 system updates it to the latest centos 7, whihc is currently 7.3. there's no such thing as 7.2 updates once 7.3 has come out. the files that say 7.1 haven't been updated since 7.1, but are still applicable to the latest.
On Thu, Jan 26, 2017 at 06:08:45PM -0600, Johnny Hughes wrote:
On 01/26/2017 06:00 PM, Jon LaBadie wrote:
My system is 7.2.1511.
When I run "yum update", it wants to install about 900 packages total. Most are labeled just "el7". A few "el7_1" and a lot are "el7_3" or 7.3. None are 7.2.
I'm not surprised when I see 50-100 packages needing an update. But 900? And none specific to the installed system?
My last update, of 4 packages, was Dec 31, 2016. I first noted the current behavior about 10 days later and have been trying to figure out why such an unusual report.
CentOS 7 is the release .. point releases (7.0.1406, 7.1.1503, 7.2.1511, 7.3.1611), are 'point in time' snapshots of the CentOS 7 tree.
CentOS has no mechanism to stay on 7.2.1511 when 7.3.1611 has been released. 7.3 and 7.2 are really just CentOS-7 with updates.
The update you are seeing is the CentOS-7 tree after we finished releasing all the 7.3.1611 packages (and updates to 7.3.1611)
On Thu, Jan 26, 2017 at 04:11:16PM -0800, John R Pierce wrote:
yum update of any centos 7 system updates it to the latest centos 7, whihc is currently 7.3. there's no such thing as 7.2 updates once 7.3 has come out. the files that say 7.1 haven't been updated since 7.1, but are still applicable to the latest.
Thanks Johnny and John.
And here I thought I had asked to upgrade to 7.2 a year ago.
A 900 package update is a concern for a computer our home relies upon to be there daily. Thus my caution.
Jon
Hello Jon,
On Thu, 2017-01-26 at 23:35 -0500, Jon LaBadie wrote:
And here I thought I had asked to upgrade to 7.2 a year ago.
Not exactly sure what you are referring to, but to elaborate on what the others said, only the latest point release is a supported release. This was 7.2.1511 (year 15, month 11) last year and it is 7.3.1612 now.
A 900 package update is a concern for a computer our home relies upon to be there daily. Thus my caution.
I don't think I'm exaggerating when I say millions of people use this release (and its upstream daddy) and do point upgrades without a hitch.
If your relatives are in the habit of pulling power then it might be cautious to perform an fsck before starting the update. You might want to check if you have enough disk space available before proceeding, although if you don't the update will just abort without any consequences (other than perhaps filling up your yum cache if you keep packages, i.e. if keepcache=1 in yum.conf). Other than that you shouldn't expect any issues. Just run that update and feel your confidence grow ;-) .
Regards, Leonard.
-
John R Pierce -
Johnny Hughes -
Jon LaBadie -
Leonard den Ottolander