Hello all, during the latest upgrade of -current I left the laptop unplugged and it got shutdown. So, I left with an unfinished upgrade. Luckily the status was in a point I could logon (after modifying lilo.conf and running lilo again) but when I tried again to do the upgrade I got

root@apost:~# slackpkg upgrade-all

FATAL! There is some problem in packages database
or maybe an installation or upgrade in progress:

kernel-source-5.15.10-noarch-1-upgraded-2021-12-22,22:24:21

If you continue you may corrupt packages database.
Check or retry later

Following an old thread here on linuxquestions
(https://www.linuxquestions.org/quest...ed-4175611777/)
I removed the package kernel-source-5.15.10-noarch-1-upgraded-2021-12-22,22:24:21 from /var/log/packages and restarted the upgrade again. It finished OK this time. But I am afraid if something left over, or something went fundamentally wrong with the upgrade. Was this action the correct one? (to delete the package listed above)

Please tell me there is a way out of this instead of doing a fresh installation all over again!

Regards, Apostolos.

I noticed an error with virtualbox. It could not build the virtualbox kernel modules, so I tried to slackpkg reinstall every package on the changelog (the last one, from 22/12). After that the virtualbox kernel modules were successfully rebuilt. It seems that this last action brought the system to a better state. Hoping a new update will come soon.

2 members found this post helpful.

Your problem seems solved, isn't it ?

I keep for this kind of failure (and several other reasons) a mirror of the packages tree. Saved me a few times when system was really borked.

Nowadays I tend to have a liveslak with the mirror on it.

It sounds like your computer shut down during the upgrade of the kernel-source package, which left it broken. Removing the file "kernel-source-5.15.10-noarch-1-upgraded-2021-12-22,22:24:21" just removed the package entry from the package database, but your problem likely wasn't fixed until you reinstalled the kernel-source package. Good job on getting it figured out!

Thanks for posting this. Hopefully others can find it if they run into issues and can see how you fixed it.

1 members found this post helpful.

Yes, it seems so. I even did today's upgrade without problem. So probably I should mark this thread as solved.

@bassmadrigal: thanks for the explanation.

1 members found this post helpful.