-current slackpkg reports broken /var/log/packages

igadoter · 03-27-2021, 08:37 PM

I am trying update system and got this from slackpkg upgrade-all

Quote:

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 is shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:

kernel-headers-5.10.23-x86-1
kernel-headers-5.11.6-x86-1
kernel-huge-5.10.23-x86_64-1
kernel-huge-5.11.6-x86_64-1
kernel-modules-5.10.23-x86_64-1
kernel-modules-5.11.6-x86_64-1

You can (R)emove, or (I)gnore these packages.
Select your action (R/I):

for me packages are ok. As I understand due to slackpkg it is wrong/not correct/broken to have different kernel versions installed. Or I am missing something. And this "don't worry" message made me laugh a little. At this point I won't update. Had no idea what slackpkg will do. Safe choice is to ignore option - but whole stuff - something is not correct with this. Say slackpkg would run without user interaction - can be a mess.

chrisretusn · 03-27-2021, 09:08 PM

I assume you are using slackpkg-15.0.1 without slackpkg+

These are the kernel packages I have installed:

Code:

find /var/lib/pkgtools/packages/ -name "kernel*" -printf "%f\n"
kernel-modules-5.11.10-x86_64-1
kernel-headers-5.11.10-x86-1
kernel-source-5.11.10-noarch-1
kernel-generic-5.11.9-x86_64-1
kernel-generic-5.10.26-x86_64-1
kernel-source-5.10.26-noarch-1
kernel-modules-5.11.9-x86_64-1
kernel-generic-5.11.10-x86_64-1
kernel-firmware-20210322_3f026a2-noarch-1
kernel-modules-5.10.26-x86_64-1
kernel-source-5.11.9-noarch-1

This is my blacklist for kernels:

Code:

kernel-generic
kernel-huge
kernel-modules
kernel-source

Code:

slackpkg upgrade-all

Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE

chrisretusn · 03-27-2021, 09:13 PM

Quote:

Originally Posted by igadoter

And this "don't worry" message made me laugh a little. At this point I won't update. Had no idea what slackpkg will do. Safe choice is to ignore option - but whole stuff - something is not correct with this. Say slackpkg would run without user interaction - can be a mess.

Selecting (R)emove will take you to a dialog selection list. Nothing is done with out confirmation.

chrisretusn · 03-27-2021, 09:15 PM

This is what it does with -dialog=off

Code:

slackpkg -dialog=off upgrade-all

Checking local integrity... DONE
You have a broken /var/log/packages/ - with multiple versions of the same package.
The list of packages duplicated in your machine is shown below:

kernel-generic-5.11.9-x86_64-1
kernel-generic-5.10.26-x86_64-1
kernel-generic-5.11.10-x86_64-1
kernel-modules-5.11.10-x86_64-1
kernel-modules-5.11.9-x86_64-1
kernel-modules-5.10.26-x86_64-1
kernel-source-5.11.10-noarch-1
kernel-source-5.10.26-noarch-1
kernel-source-5.11.9-noarch-1

You can (R)emove one or more of, or (I)gnore these packages.
Select your action (R/I): r

kernel-generic-5.11.9-x86_64-1
kernel-generic-5.10.26-x86_64-1
kernel-generic-5.11.10-x86_64-1
kernel-modules-5.11.10-x86_64-1
kernel-modules-5.11.9-x86_64-1
kernel-modules-5.10.26-x86_64-1
kernel-source-5.11.10-noarch-1
kernel-source-5.10.26-noarch-1
kernel-source-5.11.9-noarch-1

Total package(s): 9

Do you wish to remove selected packages (Y/n)? n

igadoter · 03-27-2021, 09:28 PM

Thanks. But blacklisting kernel means I would have to manage kernel updates myself. Not very happy about this. I hope rworkmaan will read this thread. He is the person. I am getting. Old default kernel is 5.10.23 - new 5.10.26 - but 5.11.x is already installed - so nothing to really update. Because 10 < 11. Seems life is little more complicated than simple arithmetic operations. I am running plain -current - no custom changes except 5.11.x installed.

Edit: I think simpler option is to remove testing kernel before upgrade. Simpler than managing all kernels. Just boot with 5.10.x remove 5.11. - upgrade with slackpkg , reinstall 5.11.x

STDOUBT · 03-28-2021, 12:32 AM

There used to be a (B)lackist option in the dialogue along with Remove and Ignore...
Manually blacklisting didn't help in my case.
I ran into the same problem, and I winged it by actually removing ALL installed kernels
in order to proceed with the update.
Made double-dog sure to re-install a few recent kernels manually before rebooting!
I don't mind manually managing kernel updates since I use LVM and generic kernels with custom initrd's, but it does seem to me slackpkg reporting multiple installs of the same kernels is some kind of weird malfunction.

chrisretusn · 03-28-2021, 01:05 AM

Quote:

Originally Posted by STDOUBT

There used to be a (B)lackist option in the dialogue along with Remove and Ignore...
Manually blacklisting didn't help in my case.
I ran into the same problem, and I winged it by actually removing ALL installed kernels
in order to proceed with the update.
Made double-dog sure to re-install a few recent kernels manually before rebooting!
I don't mind manually managing kernel updates since I use LVM and generic kernels with custom initrd's, but it does seem to me slackpkg reporting multiple installs of the same kernels is some kind of weird malfunction.

The blacklist action has been disabled.

Code:

slackpkg blacklist test

Edit /etc/slackpkg/blacklist to add or remove packages.

How is it weird? Normally there will only be one kernel version installed. By default it will be kernel-huge since that is the last of the (kernel-generic, kernel-huge) packages to be installed that set the symlinks. I see no malfunction here. A testing kernel will not be installed unless the user takes step to install it.

If wants to run muliple kernels, then one must know how to deal with it, this is not the task of slackpkg.

chrisretusn · 03-28-2021, 01:24 AM

Quote:

Originally Posted by igadoter

Thanks. But blacklisting kernel means I would have to manage kernel updates myself. Not very happy about this. I hope rworkmaan will read this thread. He is the person. I am getting. Old default kernel is 5.10.23 - new 5.10.26 - but 5.11.x is already installed - so nothing to really update. Because 10 < 11. Seems life is little more complicated than simple arithmetic operations. I am running plain -current - no custom changes except 5.11.x installed.

Edit: I think simpler option is to remove testing kernel before upgrade. Simpler than managing all kernels. Just boot with 5.10.x remove 5.11. - upgrade with slackpkg , reinstall 5.11.x

Your thinking is on the right track in my opinion. Pick one of the kernels (testing or stock) and go with that one.

The simplest is using the stock kernel 5.10.x, just let slackpkg do the upgrade. You will still have to run lilo though after a kernel is upgraded. If your using a generic kernel with will still have to rum mkinitrd. If you are not using lilo you will still have to do the task required for the boot system you are using.

If you want to use the testing kernel 5.11.x and just let slackpkg do the upgrade, you can change "PRIORITY" in slackpkg.conf to:

Code:

# Default value: patches %PKGMAIN extra pasture testing
PRIORITY=( patches testing %PKGMAIN extra pasture )

Setting this with testing as a priority only effects upgrading. Packages in testing that are not installed will not be affected by "slackpkg upgrade | upgrade-all".

Once the testing kernel is installed, it will be the kernel that is upgraded with this setting.

When the testing kernel is moved out of testing, since there is no more kernel packages in testing the stock packages will take priority. If a new testing kernel lands in testing, that will be used to upgrade the stock kernel. Of course this all happens after you approve it via the dialog box. You can always set "PRIOROTY" back to the default if you don't want this to happen.

I do this with a few machine that us the kernel-huge. That are using the testing kernel 5.11.10

On my machines with multiple kernels installed I wrote a script to handle kernel upgrading.

STDOUBT · 03-28-2021, 01:28 AM

Quote:

Originally Posted by chrisretusn

How is it weird?

Let me tell you how it's weird:
I have installed 3 different kernels for example,

Code:

kernel-generic-smp-4.4.14_smp-i686-1
kernel-generic-smp-5.10.19_smp-i686-1
kernel-generic-smp-5.10.20_smp-i686-1

and obviously as well, the corresponding modules,

Code:

kernel-modules-smp-4.4.14_smp-i686-1
kernel-modules-smp-5.10.19_smp-i686-1
kernel-modules-smp-5.10.20_smp-i686-1

When slackpkg runs and tells me /var/log/packages/ is broken,
and then I look at it, only those things appear and they are NOT duplicates.
BUT when I run (R)emove, pkgtool lists four separate instances of each kernel and each modules packages as so:

Code:

kernel-generic-smp-4.4.14_smp-i686-1
kernel-generic-smp-5.10.19_smp-i686-1
kernel-generic-smp-5.10.20_smp-i686-1
kernel-modules-smp-4.4.14_smp-i686-1
kernel-modules-smp-5.10.19_smp-i686-1
kernel-modules-smp-5.10.20_smp-i686-1
kernel-generic-smp-4.4.14_smp-i686-1
kernel-generic-smp-5.10.19_smp-i686-1
kernel-generic-smp-5.10.20_smp-i686-1
kernel-modules-smp-4.4.14_smp-i686-1
kernel-modules-smp-5.10.19_smp-i686-1
kernel-modules-smp-5.10.20_smp-i686-1
kernel-generic-smp-4.4.14_smp-i686-1
kernel-generic-smp-5.10.19_smp-i686-1
kernel-generic-smp-5.10.20_smp-i686-1
kernel-modules-smp-4.4.14_smp-i686-1
kernel-modules-smp-5.10.19_smp-i686-1
kernel-modules-smp-5.10.20_smp-i686-1
kernel-generic-smp-4.4.14_smp-i686-1
kernel-generic-smp-5.10.19_smp-i686-1
kernel-generic-smp-5.10.20_smp-i686-1
kernel-modules-smp-4.4.14_smp-i686-1
kernel-modules-smp-5.10.19_smp-i686-1
kernel-modules-smp-5.10.20_smp-i686-1

That's weird, that's wrong, and IMO something is broken.
Again NO duplicates of these packages exist in /var/log/packages/.

To be clear, some months ago this did not happen even with up to 7 different kernels installed.

chrisretusn · 03-28-2021, 01:51 AM

Well that is weird. It does not happen here.
This is my /boot/:

Code:

ls -l vmlinuz* System.map* config*
lrwxrwxrwx 1 root root      26 Mar 26 23:00 System.map -> System.map-generic-5.11.10
-rw-r--r-- 1 root root 4879843 Mar 26 04:49 System.map-generic-5.10.26
-rw-r--r-- 1 root root 4912023 Mar 26 04:25 System.map-generic-5.11.10
-rw-r--r-- 1 root root 4912023 Mar 25 03:54 System.map-generic-5.11.9
lrwxrwxrwx 1 root root      26 Mar 26 23:00 config -> config-generic-5.11.10.x64
-rw-r--r-- 1 root root  230159 Mar 26 02:13 config-generic-5.10.26.x64
-rw-r--r-- 1 root root  232397 Mar 26 02:13 config-generic-5.11.10.x64
-rw-r--r-- 1 root root  232396 Mar 25 02:35 config-generic-5.11.9.x64
lrwxrwxrwx 1 root root      23 Mar 26 23:00 vmlinuz -> vmlinuz-generic-5.11.10
lrwxrwxrwx 1 root root      23 Mar 26 23:00 vmlinuz-generic -> vmlinuz-generic-5.11.10
-rw-r--r-- 1 root root 7099104 Mar 26 04:49 vmlinuz-generic-5.10.26
-rw-r--r-- 1 root root 7156544 Mar 26 04:25 vmlinuz-generic-5.11.10
-rw-r--r-- 1 root root 7156960 Mar 25 03:54 vmlinuz-generic-5.11.9
lrwxrwxrwx 1 root root      23 Mar 26 23:00 vmlinuz-generic-stock -> vmlinuz-generic-5.10.26
lrwxrwxrwx 1 root root      23 Mar 26 23:01 vmlinuz-generic-testing -> vmlinuz-generic-5.11.10
lrwxrwxrwx 1 root root      22 Mar 26 22:59 vmlinuz-generic-working -> vmlinuz-generic-5.11.9

Here are the package that are installed.

Code:

ls -l /var/lib/pkgtools/packages/kernel*
-rw-r--r-- 1 root root   96623 Mar 23 17:14 /var/lib/pkgtools/packages/kernel-firmware-20210322_3f026a2-noarch-1
-rw-r--r-- 1 root root    1027 Mar 26 22:59 /var/lib/pkgtools/packages/kernel-generic-5.10.26-x86_64-1
-rw-r--r-- 1 root root    1043 Mar 26 23:00 /var/lib/pkgtools/packages/kernel-generic-5.11.10-x86_64-1
-rw-r--r-- 1 root root    1038 Mar 25 19:53 /var/lib/pkgtools/packages/kernel-generic-5.11.9-x86_64-1
-rw-r--r-- 1 root root   30150 Mar 26 22:55 /var/lib/pkgtools/packages/kernel-headers-5.11.10-x86-1
-rw-r--r-- 1 root root  316091 Mar 26 23:00 /var/lib/pkgtools/packages/kernel-modules-5.10.26-x86_64-1
-rw-r--r-- 1 root root  319034 Mar 26 23:00 /var/lib/pkgtools/packages/kernel-modules-5.11.10-x86_64-1
-rw-r--r-- 1 root root  313553 Mar 25 19:53 /var/lib/pkgtools/packages/kernel-modules-5.11.9-x86_64-1
-rw-r--r-- 1 root root 4933070 Mar 26 23:00 /var/lib/pkgtools/packages/kernel-source-5.10.26-noarch-1
-rw-r--r-- 1 root root 4981589 Mar 26 23:01 /var/lib/pkgtools/packages/kernel-source-5.11.10-noarch-1
-rw-r--r-- 1 root root 4895686 Mar 25 19:54 /var/lib/pkgtools/packages/kernel-source-5.11.9-noarch-1

Here is slackpkg with no kernels blacklisted.

Code:

slackpkg upgrade-all

Checking local integrity... DONE
You have a broken /var/log/packages/ - with multiple versions of the same package.
The list of packages duplicated in your machine is shown below:

kernel-generic-5.11.9-x86_64-1
kernel-generic-5.10.26-x86_64-1
kernel-generic-5.11.10-x86_64-1
kernel-modules-5.11.10-x86_64-1
kernel-modules-5.11.9-x86_64-1
kernel-modules-5.10.26-x86_64-1
kernel-source-5.11.10-noarch-1
kernel-source-5.10.26-noarch-1
kernel-source-5.11.9-noarch-1

You can (R)emove one or more of, or (I)gnore these packages.
Select your action (R/I):

Selecting (R)emove give me a selection list to decide which kernels to remove.

Code:

kernel-generic-5.11.9-x86_64-1
kernel-generic-5.10.26-x86_64-1
kernel-generic-5.11.10-x86_64-1
kernel-modules-5.11.10-x86_64-1
kernel-modules-5.11.9-x86_64-1
kernel-modules-5.10.26-x86_64-1
kernel-source-5.11.10-noarch-1
kernel-source-5.10.26-noarch-1
kernel-source-5.11.9-noarch-1

igadoter · 03-28-2021, 03:04 AM

To run testing and default is safe choice in case testing will brake something. I did as posted earlier. Once packages for kernel 5.11.x were removed warning disappeared. I did all upgrades. Once slackpkg finished I upgraded kernel 5.11.6 to 5.11.10. The last installed huge kernel is linked by vmlinuz. I boot with grub coming from Devuan. I dislike grub like hell. I update only when updates for Devuan are available. I decided to stay away at this moment from grub. In terms of learning it. Devuan updates grub auto-magically during kernel update. -current updates kernel - once per week? Running grub such often makes feel uncomfortable. I mean I have local mirror. I update mirror - and when Devuan provides kernel update - I update kernels on Slackware first and on Devuan later. I keep grub exactly because of Devuan. Debian and derivatives are don't-touch distributions. Just follow recipes. If grub is default boot-loader - keep it.

Edit: rebooted with kernel 5.10.23 and then removed 5.11.x

Edit: Joking I could say new version of grub should be given codename: Ever Given ;D