usm: old porteus - usm -u all fails, what to do now?

[att]

Hello,
Sorry, I am running a very old porteus....

root@porteus:~/bin# uname -a
Linux porteus 3.13.6-porteus #1 SMP PREEMPT Fri Mar 7 06:53:36 Local time zone must be set--s x86_64 Intel(R) Atom(TM) CPU S1260 @ 2.00GHz GenuineIntel GNU/Linux


.... and I wanted to update the usb database :

porteus:~/bin# usm -u all
Starting alien database update
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz DONE

gzip: /var/usm/alien/CHECKSUMS.md5.gz: unexpected end of file


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

FATAL ERROR!
usm update_database 184
Could not decompress: CHECKSUMS.md5.gz

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

Now that is the error I get.
Is there any way to install packages even when not all databases are updated?

Please tell me what to do to get more packages installed.

[Ed_P]

You could try commenting out the problem database in /etc/usm/usm.conf. Or you could try updating to a newer version of Porteus.

[beny]

hi att, for first aid you can search packages with this link: https://slackware.nl/slakfinder/ .
and why you don't extract the script slapt-mod from a new porteus located to /usr/local/bin and try if work on your old system,you need slapt-get package tweak the configure with your repositories and update as usm -u

[Ed_P]

I don't know beny, does the old USM system include get-mod and the /var/lib/pkgtools/packages/ files that I think slapt-mod uses? Not saying slapt-mod can't work in 3.13 just that it will require more than just the slapt-mod file from 5.01.

[beny]

well he can try if work get-mod,i think that don't depend from glibc or the gcc,but only the network software

[att]

Commenting out the single problematic database seems to be a good choice, I'll try and let you know!