Page 1 of 1

LIBS.TXT error in USM

Posted: 22 Jul 2019, 14:50
by pblack476
I know this pops up from time to time but I am getting this error when using USM (after updating all repos) and I cannot set up anything in my new installation of Porteus v5

I appreciate any help on the matter.

LIBS.TXT error in USM

Posted: 22 Jul 2019, 14:57
by Ed_P
Check out the links in this thread. USM - Updates fail (Post by Ed_P #60166)

This may help also. USM - Updates fail (Post by Ed_P #73005)

LIBS.TXT error in USM

Posted: 22 Jul 2019, 16:39
by pblack476
Thanks @Ed_P

I've done what your post describes and got " There was a problem downloading the file:" in the slackware repo. Ran safm.sh and got no improvement with any mirror.

According to your second link I've rerun sasm.sh and still nothing changed. I should now:
2. manually tweak the problem mirror's mirror list files.
And that is where I do not know where to proceed. What is the part of the post that I should be following now?

LIBS.TXT error in USM

Posted: 22 Jul 2019, 17:27
by Ed_P
Manually edit the /etc/usm/mirrors-slackware.txt file, as root. Find the active mirror, the URL without a # in front of it, add a # to the front of it, and then find a mirror that you think may be better and remove it's # sign. I usually choose URLs located closer to where I am at the time.

LIBS.TXT error in USM

Posted: 22 Jul 2019, 18:56
by pblack476
Ed_P wrote:
22 Jul 2019, 17:27
Manually edit the /etc/usm/mirrors-slackware.txt file, as root. Find the active mirror, the URL without a # in front of it, add a # to the front of it, and then find a mirror that you think may be better and remove it's # sign. I usually choose URLs located closer to where I am at the time.
Done that and no luck. I tried several other mirrors and all return the same error on LIBS.TXT for slackware.

I know this works becuase I had to do the same for salix as it was hanging on CHECKSUM.md5 and it worked when I chose another mirror. But slackware is being stubborn.

LIBS.TXT error in USM

Posted: 23 Jul 2019, 04:27
by Ed_P
All you can do is wait for the next Slackware mirror updates to hopefully correct the problem. :(