LinuxQuestions.org - Slackware -current. Slackpkg ended with warning: incorrect md5sum during upgrade

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware -current. Slackpkg ended with warning: incorrect md5sum during upgrade (https://www.linuxquestions.org/questions/slackware-14/slackware-current-slackpkg-ended-with-warning-incorrect-md5sum-during-upgrade-4175661747/)

Slackware -current. Slackpkg ended with warning: incorrect md5sum during upgrade

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.

About initrd and mkinitrd rerun message.
May be filtering lilo.conf comments can fix this:
/usr/libexec/slackpkg/functions.d/post-functions.sh

Code:

-                if [ -x /sbin/lilo ] && [ -r /etc/lilo.conf ] && grep -q initrd /etc/lilo.conf ; then

+                if [ -x /sbin/lilo ] && [ -r /etc/lilo.conf ] && grep -v '^\s*#' /etc/lilo.conf | grep -q initrd ; then

Thanks I will have look at this. Till now system works. I am much more worried about mismatch mdsum warning. Something went wrong. No idea what. Disk failure during file copy? Does it possible to reconfigure slackpkg to use local repository (mirror) instead of local or remote ftp/http server? This will avoid necessity to copy files from place to another. I would sync mirror and then slackpkg would install directly from my own local mirror Now it access it through ftp service. Connects and copies them into its own cache. From my point it is the same work done twice.

Edit: It is generally good idea to add parser to slackpkg which will be capable to ignore all lines commented out. Then look for initrd. Possible spaces, tabs at the start of line followed by #. Correct parser is of course contained in lilo - it reads lilo.conf and skips all commented out lines. So preferably we should go the way lilo goes.