[SOLVED] intel-microde: INSTALLED PACKAGE IS NEWER THAN REPO

PreguntoYo · 03-05-2018, 06:46 AM

Hello:

I noticed this message today, while trying to update the intel-microcode SBo package in my Slackware 64 14.2 stable.

I thought I had the most up to-date version:

intel-microcode-20180108-noarch-1_SBo

But sbopkg proposes updating to an older version?:

intel-microcode-20171117-noarch-1_SBo

Is this correct?. Have I missed something?

GazL · 03-05-2018, 06:55 AM

Intel recalled the 0108 package as it was causing issues, so most people (including SBo it seems) reverted to the 1117 release: which is still listed as the latest version on the intel download page.

Didier Spaier · 03-05-2018, 07:02 AM

I am not sure what command you typed, but any application that relies on upgradepkg will just replace an installed package by another one found proposed for "upgrade", as long as the short name is the same but the versions or build tags differ.

upgradepkg neither knows nor cares which is newer between the two, and the newer is not always the better, as Gazl just posted while I was still writing. That's your task, as a user, to know what you are doing.

This has been stated in several thread in this forum.

PreguntoYo · 03-05-2018, 07:17 AM

Quote:

Originally Posted by Didier Spaier

I am not sure what command you typed, but any application that relies on upgradepkg will just replace an installed package by another one found in the source repository, as long as the short name is the same but the versions or build tags differ.

upgradepkg neither knows nor cares which is newer between the two, and the newer is not always the better, as Gazl just posted while I was still writing. That's your task, as a user, to know what you are doing.

This has been stated in several thread in this forum.

I just let Sbopkg check if there were any updates to my installed packages. I found something that seemed "strange" to me and decided to ask before typing anything else. I thought other people could have the same doubt.

How may I say it... it's difficult to keep with the news lately; Meltdown, Spectre, kernel upgrades, Intel microcode (reverting to an older version)...

I know that Slackware can let you revert to older versions of packages, but I haven't done this many times since I started with Slackware.

mlangdn · 03-05-2018, 07:27 AM

PreguntoYo - it was a good question, and Gazl had the answer as to why it was different. If all of us knew what we were doing, we wouldn't need Linuxquestions. I would have asked too.

Didier Spaier · 03-05-2018, 07:43 AM

Quote:

Originally Posted by PreguntoYo

I found something that seemed "strange" to me and decided to ask before typing anything else. I thought other people could have the same doubt.

And rightly so. Sorry if my previous answer looked harsh.

orbea · 03-05-2018, 09:13 AM

Quote:

Originally Posted by Didier Spaier

I am not sure what command you typed

I'd guess it was 'sbopkg -c'.

PreguntoYo · 03-05-2018, 04:07 PM

Quote:

Originally Posted by Didier Spaier

And rightly so. Sorry if my previous answer looked harsh.

No problem.

I let upgradepkg revert to the older version (I still had the package around):

Code:

# upgradepkg intel-microcode-20180108-noarch-1_SBo%intel-microcode-20171117-noarch-1_SBo.tgz

I think my command could be simplified, anyway it worked to me.

Thanks for your help.

bassmadrigal · 03-05-2018, 06:44 PM

Quote:

Originally Posted by PreguntoYo

Code:

# upgradepkg intel-microcode-20180108-noarch-1_SBo%intel-microcode-20171117-noarch-1_SBo.tgz

I think my command could be simplified, anyway it worked to me.

The only time you need to run the upgradepkg command like that is when the package names have changed. This allows upgradepkg to know what the old package name is so it can upgrade it with the new one.

In this case, all you needed to run was the following, but your method still works, it's just more typing

Code:

upgradepkg /location/to/intel-microcode-20171117-noarch-1_SBo.tgz