[SOLVED] kernel-headers

Lysander666 · 04-29-2019, 01:40 PM

As title, really. In stable, the process I use is installpkg for

source
modules
huge
generic

and then upgradepkg for

headers
firmware

I then remove the old packages manually.

In -current I'm confused. Using upgradepkg for the firmware is a given, but installpkg or upgradepkg for the headers [I want to keep the old kernel]?

rkfb · 04-29-2019, 01:58 PM

I always upgradepkg firmware and installpkg headers along with source, generic etc. I don't see the harm.

bassmadrigal · 04-30-2019, 12:48 AM

The kernel-headers package will almost completely replace the previous headers in the system (in reality, they are more of glibc-headers and aren't used for almost all programs -- the kernel headers that are used by almost all programs and all modules are in the kernel source tree, /usr/src/linux-4.19.x/include/, whereas the kernel-headers headers are in /usr/include/). Various kernel-headers don't coexist like kernel-{generic,huge,modules,source} do. installpkg will only overwrite any existing headers with the ones from the current package and will likely leave older, stale headers that could potentially cause issues.

You can always double check by running the following and seeing how many files it would overwrite:

Code:

installpkg --warn /location/to/kernel-headers-*.t?z

So, just keep doing the process you have listed above. installpkg for everything but kernel-headers and kernel-firmware and use upgradepkg on those.

Lysander666 · 04-30-2019, 04:19 AM

Quote:

Originally Posted by bassmadrigal

The kernel-headers package will almost completely replace the previous headers in the system (in reality, they are more of glibc-headers and aren't used for almost all programs -- the kernel headers that are used by almost all programs and all modules are in the kernel source tree, /usr/src/linux-4.19.x/include/, whereas the kernel-headers headers are in /usr/include/). Various kernel-headers don't coexist like kernel-{generic,huge,modules,source} do. installpkg will only overwrite any existing headers with the ones from the current package and will likely leave older, stale headers that could potentially cause issues.

You can always double check by running the following and seeing how many files it would overwrite:

Code:

installpkg --warn /location/to/kernel-headers-*.t?z

So, just keep doing the process you have listed above. installpkg for everything but kernel-headers and kernel-firmware and use upgradepkg on those.

Thanks, bass. So I'll use exactly the same procedure. In which I'll just upgradepkg on those headers I've already installed for 4.19.37.

EDIT: after running slackpkg upgrade-all I got the following notification:

Code:

Checking local integrity... DONE
You have a broken /var/log/packages/ - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:

kernel-headers-4.19.34-x86-1
kernel-headers-4.19.37-x86-1

So you were right [of course]. I removed the older headers.

bassmadrigal · 04-30-2019, 10:34 AM

Quote:

Originally Posted by Lysander666

EDIT: after running slackpkg upgrade-all I got the following notification:

Code:

Checking local integrity... DONE
You have a broken /var/log/packages/ - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:

kernel-headers-4.19.34-x86-1
kernel-headers-4.19.37-x86-1

So you were right [of course]. I removed the older headers.

All this means is at some point you did an installpkg on a second kernel-headers package, but you didn't have it blacklisted in slackpkg. If you removed the other kernel entries from your blacklist, you'd see the same thing. This does not indicate that a package conflicts with itself, just that you have two or more of the same packages installed on the system.

You would need to either run a comparison of both the entries or run installpkg --warn /location/to/package.t?z to find out how much a package will conflict with another package.

orbea · 04-30-2019, 10:40 AM

With slackpkg I use upgradepkg on kernel-headers, the list of files installed in this package would probably conflict with other versions easily and you are likely overwriting them with installpkg. I would guess this defeats the point of installing two different versions of the package.

rkfb · 04-30-2019, 01:46 PM

What do I know?

bassmadrigal · 04-30-2019, 03:19 PM

Quote:

Originally Posted by rkfb

What do I know?

Most likely, it won't hurt anything. The only chance is if a program checks for a header that should no longer exist and then it enables functionality that doesn't exist in the rest of the headers. But very few programs actually build against the headers in /usr/include/, so the chances of that happening are likely very slim.