Porteus - USM error

[yldouright]

Yeah, root got rid of it, thanks. Okay, so USM on Porteus 3.2.2 is acting weird on a Dell E6510 laptop install of Mate. I had the same issue on Mate with v3.2.0. After a fresh install you open USM and get the "Missing database files" message. You check and discover USM is the latest version but clicking download for "test-package-name-1.2.3-x86_64-1.txz" times out with no feedback in the terminal. You can't "USM:Updates:Update all" now that Salix and other databases are defunct (that command led to a broken system). I fixed this last time by editing my sources but is there an easier way to resolve this?

[Ed_P]

Yes, the 1st time you use USM on a new install you have to update the database(s), they are all empty. Yes, if a mirror is having problems you have to edit the source files. BUT this is a lot easier by using the sesm.sh script found here: [INFO & SCRIPT] Slackware Mirror Settings for USM

[yldouright]

Thanks Ed, do we have a list of the current "good sources" anywhere? If not, I'll post them in the bugs forum or make a tutorial. What do you make of the "test-package-name-1.2.3-x86_64-1.txz" download failure described in the post above? The link you provided starts with the "time usm -u all" command which has broken my install before so I'm hesitant to use it. Where do I get the "sesm.sh all" script? Why wouldn't it be better to just comment out or enable the lists in the "usm:settings:edit configuration files" command?

[yldouright]

I'm experiencing the same on a Dell E6510 laptop, fresh install of Porteus 3.2 with Mate. USM states it is the latest version if you try to update it. The update all command breaks the system. I mentioned the problem in this post. It seems the database doesn't update via USM.

[Ed_P]

Thanks Ed, do we have a list of the current "good sources" anywhere?

Run the script and you will have a list. But the lists vary depending on the users location so what you might post for NY may not work as well for someone in Australia.

The link you provided starts with the "time usm -u all" command

You need to read the link again. The "usm -u all" command is number 2.. Number 1 is run the sesm.sh script.

Where do I get the "sesm.sh all" script?

It's after the number 4 point. Copy and paste it into your /home/guest/ folder.

Why wouldn't it be better to just comment out or enable the lists in the "usm:settings:edit configuration files" command?

That works but IMHO the sesm.sh script is a whole lot faster and does a better job.

What do you make of the "test-package-name-1.2.3-x86_64-1.txz" download failure described in the post above?

It's a dummy test name nothing more, shown simply as an example.

Example Tutorial

1. Before starting USM download (copy & paste to your /home/guest/ folder) and run the sesm.sh script. USM UPDATE PROCEDURE
2. Start USM.
3. Click Update > Update All
4. Disregard the example test package name. It's not a real file name.

[Ed_P]

Response posted here: Firefox Quantum

And I just updated my USM databases using the USM GUI with no problem.

[yldouright]

@Ed_P
Noted and thanks for the hand holding. I've assumed the ones on the top of that thread are the latest versions of these scripts. I copied those 3 scripts (sesm.sh, safm.sh and badm.sh) to plain text files from the 'code:select all' button and will run them as root as directed but before I do, I'm going to review what I think needs to be done first.
1. In the USM:Settings:Edit Configurations, do I need to uncomment all the mirrors in those or leave them be?
2. What is the following code excerpt from that page and where/how is it used? Does the code excerpt below add new mirrors that should be included in the USM configuration lists or is just output from one of the three scripts?
Downloading: extra-deps.txt DONE
Downloading: ignore-deps.txt DONE
3. If I need to remove any of the depository comments from USM, what is the best way to do this?
4. Does the 'safm.sh' script automatically write and append the .usm/badmirrors.txt if the .usm directory exists?
5. The badm.sh script appears to have only one line in it, is this correct?

[Ed_P]

I've assumed the ones on the top of that thread are the latest versions of these scripts.

A valid assumption.

1. In the USM:Settings:Edit Configurations, do I need to uncomment all the mirrors in those or leave them be?

Leave them be.

2. What is the following code excerpt from that page and where/how is it used? Does the code excerpt below add new mirrors that should be included in the USM configuration lists or is just output from one of the three scripts?
Downloading: extra-deps.txt DONE
Downloading: ignore-deps.txt DONE

It is the output of running a script.

3. If I need to remove any of the depository comments from USM, what is the best way to do this?

I would leave them alone, I see no need to remove them.

4. Does the 'safm.sh' script automatically write and append the .usm/badmirrors.txt if the .usm directory exists?
5. The badm.sh script appears to have only one line in it, is this correct?

I've never had a need to use them so I don't know. But I believe the answers to both is Yes.

[yldouright]

Where do we store the scripts to run them? Is the Pluma folder appropriate or is there a better place?

[Ed_P]

I use /home/guest/ for most of my scripts but for these and a couple of others I made a subfolder named USM so I wouldn't loose them. To execute I would open a terminal and enter:

su
pswd
sh USM/sesm.sh all

If I were executing them a lot I would use "chmod +x USM/*.sh" and then execute them via the file manager.

This /home/guest/USM script that I have might interest you also.

Code: Select all

#!/bin/bash
# https://forum.porteus.org/viewtopic.php?f=140&t=6966&p=55568#p55562

[[ -e /usr/share/usm/funcpackageGet.bak ]] || sudo cp -p /usr/share/usm/funcpackageGet  /usr/share/usm/funcpackageGet.bak  # Save original
#cp   /Path/to/funcpackageGet.hic    /usr/share/usm/funcpackageGet
sudo  cp    USM/*.hic                /usr/share/usm/funcpackageGet 

[Ed_P]

I put the three aforementioned scripts in a folder named "usm scripts" in my guest Documents directory.

Make sure you put quotes around the name when you execute them.

su
pswd
sh Documents/"usm scripts"/sesm.sh all

[Ed_P]

!!!! All USM updates give:

Code: Select all

gzip: /var/usm/slackware/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/slackwarepatches/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/slacky/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/salix/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/alien/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/ponce/LIBS.TXT.gz: not in gzip format
gzip: /var/usm/slackonly/LIBS.TXT.gz: not in gzip format

Houston, we have a problem.

[donald]

Houston, we have a problem.

Not we, but Sourceforge has.
The LIBS.TXT files are html files - you can use

Code: Select all

hexdump -C LIBS.TXT.gz

to view its content:
--> We're sorry -- the Sourceforge site is currently in Disaster Recovery mode...
Please check back later.<--

[Ed_P]

What's Sourceforge got to do with this?? I know SourceForge is under a DoS attack but I thought all the Slackware files were stored on the mirrors' sites.

[donald]

I thought all the Slackware files were stored on the mirrors' sites.

Apparently not - example:
sourceforge.net/projects/usm/files/14.2/db/slackware/x86_64/
I did not want it to be a link - I'm sure you know how to copy it into a new (browser) tab.