I use my own local mirror for Slackware 64 -current. I use AlieBob mirror-current.sh script. I synced mirror. Then I started slackpkg to upgrade system, slackpkg version 2.83.0. I noticed following strange behavior: slackpg because kernel was updated told to rerun mkinitrd because it thinks there is kernel with initrd ram disk. Slackpkg refers to this part of /etc/lilo.conf
Code:
# cat /etc/lilo.conf
.........
#image = /mnt/hd/boot/swsetup/bzImage
# initrd = /mnt/hd/boot/swsetup/initrd.img
# addappend = "load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s"
# label = SwSetup
.........
but pure clean it is commented out - so why slackpkg told to rerun mkinitrd? File /etc/lilo.conf is very old - but I don't recall that after earlier updates there was message about to rerun mkinitrd. The next thing is that slackpkg gave me warning about md5sum mismatch packages aaa_elflibs-15.0-x86_64-11.txz and glibc-solibs-2.30-x86_64-1.txz. So I went to directory where I keep mirror and manually verified checksums against these files on my local mirror. I was suspecting possible mirror corruption because of disk failure. Yet manual verification showed that these files are ok. I calculated checksums for them and they are correct. So I reinstalled those packages with installpkg command. I don't know but for me actions of slackpg seems to be rather strange. I hope after reboot system will work.