[SOLVED] Warning of several errors as slackpkg ran under full install of slackware live DAW

fredmyra · 12-16-2023, 01:01 PM

I have just installed slackware64-live-daw-15.0 and proceeded to update with:

Code:

slackpkg update
slackpkg upgrade-all

I did not notice anything special during the upgrading but once I confirmed the new .config files I got a warning of errors (which I understand to be of md5sum)
as below:

Code:

        Press SPACE for more, ENTER to skip 

What do you want (K/O/R/P)?

        (K)eep the old files and consider .new files later

        (O)verwrite all old files with the new ones. The
           old files will be stored with the suffix .orig

        (R)emove all .new files

        (P)rompt K, O, R selection for every single file
O
         

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                       

ca-certificates-20231117-noarch-1_slack15.0.txz:        md5sum
kernel-headers-5.15.139-x86-1.txz:      md5sum
libX11-1.8.7-x86_64-1_slack15.0.txz:    md5sum
libXpm-3.5.17-x86_64-1_slack15.0.txz:   md5sum
libarchive-3.7.2-x86_64-1_slack15.0.txz:        md5sum
libcaca-0.99.beta20-x86_64-1_slack15.0.txz:     md5sum
libcue-2.2.1-x86_64-4_slack15.0.txz:    md5sum
libnotify-0.8.3-x86_64-1_slack15.0.txz: md5sum

==============================================================================

I suspect this may not be serious but I felt obliged to inform.

P.S. : In retrospect, I just became aware that I jumped over

Code:

slackpkg update gpg

Could that explain the warning?

I have now done:

Code:

root@esprimo_Q:~# slackpkg update gpg

                        Getting key from https://www.slackware.com/infra/keys/GPG-KEY
                        Slackware Linux Project's GPG key added

root@esprimo_Q:~# slackpkg update

Updating the package lists...
        Downloading...
                        Downloading https://mirrors.slackware.com/slackware/slackware64-15.0/CHECKSUMS.md5.asc...
--2023-12-16 19:57:15--  https://mirrors.slackware.com/slackware/slackware64-15.0/CHECKSUMS.md5.asc
Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213
Connecting to mirrors.slackware.com (mirrors.slackware.com)|207.223.116.213|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 163 [text/plain]
Saving to: ‘/tmp/slackpkg.qDW2Tf/CHECKSUMS.md5.asc’

/tmp/slackpkg.qD 100%[=========>]     163  --.-KB/s    in 0s      

2023-12-16 19:57:16 (179 MB/s) - ‘/tmp/slackpkg.qDW2Tf/CHECKSUMS.md5.asc’ saved [163/163]


                No changes in ChangeLog.txt between your last update and now.
                Do you really want to download all other files (y/N)? n

root@esprimo_Q:~# slackpkg upgrade-all

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

No packages match the pattern for upgrade. Try:

        /usr/sbin/slackpkg install|reinstall

So it seems it was not that serious, but I am informing anyway as I am not able to come to any conclusion by myself. Things seem to be running well so far.

TheTKS · 12-17-2023, 06:55 AM

I always run, on both 15.0 and -current (but I don’t run live-daw), in this order:

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

You could just watch the changelog, and I do watch it, but while on stable (15.0) install-new and clean-system almost never have anything to do, certainly install-new does rarely and did recently. I run all four to ensure I didn’t miss anything.

You shouldn’t need to run

Code:

slackpkg update gpg

again on the same version of Slackware. You should read up on when you should do it (reminder to me to re-read that.)

When I get md5 errors, I reinstall each of the packages individually until there are no more errors:

Code:

slackpkg reinstall package-name.txz

Usually they reinstall without errors, occasionally I have had to reinstall a second time.
I’m not sure why that list of errors shows up. A guess: maybe you were upgrading packages while your mirror was syncing, or something glitched while the download was happening. Someone who knows can give you a better answer.

I blacklist the kernel packages and download them and do that upgrade manually with installpkg and upgradepkg.

Edit: fredmyra, I edited to elaborate on how I go about upgrading kernel packages, and why I don't use slackpkg for kernel upgrades, but unfortunately I didn't save a copy of my text, and Cloudflare stepped in and clobbered my edit when I tried to save it. If you're interested, I'll rewrite my edit.

TheTKS

fredmyra · 12-19-2023, 12:19 PM

Quote:

posted by @TheTKS
I edited to elaborate on how I go about upgrading kernel packages, and why I don't use slackpkg for kernel upgrades, but unfortunately I didn't save a copy of my text, and Cloudflare stepped in and clobbered my edit when I tried to save it. If you're interested, I'll rewrite my edit

This question has been so problematic to me that I would sure appreciate to learn from your experience, if it is not too much of a problem - I hate to rewrite stuff, so please be comfortable.

TheTKS · 12-21-2023, 06:24 AM

Quote:

Originally Posted by fredmyra

This question has been so problematic to me that I would sure appreciate to learn from your experience, if it is not too much of a problem - I hate to rewrite stuff, so please be comfortable.

fredmyra, something has come up and I won't be able to rewrite my edit soon, so in the meantime, you might find this LQ blog by @lysander666 helpful. Adapt it to your situation and look for updates, if any, to the parts that you use.

TKS

https://www.linuxquestions.org/quest...ackware-37876/

fredmyra · 12-21-2023, 08:35 PM

Quote:

posted by @TTheTKS:
fredmyra, something has come up and I won't be able to rewrite my edit soon, so in the meantime, you might find this LQ blog by @lysander666 helpful. Adapt it to your situation and look for updates, if any, to the parts that you use.

Thank you so much THETKS !

TheTKS · 02-17-2024, 07:53 AM

@fredmyra, I'm just getting back to this now as the past couple of months have been a little trying.

I rediscovered posts I had already written, so I will just link those here with a couple of notes & updates:

- I use the generic kernel

- Those links refer to Slackware 14.2, but the steps work the same on 15.0, with one addition: the geninitrd command can be used in place of the mkinitrd generator steps.

https://www.linuxquestions.org/quest...ml#post6269435

https://www.linuxquestions.org/quest...ml#post6269436

- Nowadays, instead of upgrading the headers and firmware with # slackpkg upgrade, I download those also (and verify with gpg) and then upgrade them as, for example,

Code:

# upgradepkg kernel-headers-5.15.145-x86-1.txz kernel-firmware-20231222_a7dee43-noarch-1.txz

- In the final step, I remove the kernel a little differently. Example: # removepkg kern*5.15.139*. I add "kern" in case there is another package with the same numbering (yes, it did happen to me once.)

- In those posts, I mentioned doing other package updates before the kernel updates, but I don't know if order matters as long as you keep packages (kernel and other) fairly up to date. In -current, I don't upgrade the kernel every time a new set is released, but do keep other packages pretty up to date (at least every time any update is flagged as a security fix.) In -current, I sometimes fall behind as as far as two kernel updates. That seems not to have caused me problems, but I wouldn't advise anyone else to rely on that, and on 15.0 I always update the kernel packages at the first opportunity.

fredmyra · 02-18-2024, 07:03 PM

@TheTKS: kind of you to remember and take your time. Much appreciated. It will take me some time to read and digest all of it, I am also under pressure.

I think it would be right to mark this as solved.

Thank you so much!