[Solved] restarting USM??

Post here if you are a new Porteus member and you're looking for some help.
Bob1414
Black ninja
Black ninja
Posts: 33
Joined: 28 Mar 2021, 15:35
Distribution: Cinnamon 4 kernel5.11.13 p

[Solved] restarting USM??

Post#1 by Bob1414 » 10 Apr 2021, 13:30

I've finally been able to Update All via the GUI after increasing the size of /changes/save.dat. However, the popped-up terminal window always says:
Please restart the application to refresh the database.
I've closed and restarted the GUI USM, I've shut down and restarted Porteus/Cinnamon. That accomplishes nothing. So what does it want?

I'm trying to install Thunderbird, is there alternatively a way to just directly get the URL and then download the xzm directly into /porteus/modules? Thanks.

[Edit: when I try to get Thunderbird via the USM GUI, it tells me to wait 6 hours because it could not find LIBS.T]
Last edited by Bob1414 on 12 Apr 2021, 12:54, edited 1 time in total.

Bob1414
Black ninja
Black ninja
Posts: 33
Joined: 28 Mar 2021, 15:35
Distribution: Cinnamon 4 kernel5.11.13 p

restarting USM??

Post#2 by Bob1414 » 10 Apr 2021, 14:05

Code: Select all

root@porteus:/home/guest# usm -s thunderbird

mozilla-thunderbird-68.12.0-x86_64-1_slack14.2.txz was found in slackwarepatches [not installed]
mozilla-thunderbird-45.1.1-x86_64-1.txz was found in slackware [not installed]
Packages found:   2 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download

root@porteus:/home/guest# usm -g mozilla-thunderbird-68.12.0-x86_64-1_slack14.2.txz
wget: option requires an argument -- 'P'
wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.

 Nothing found for:  mozilla-thunderbird-68.12.0-x86_64-1_slack14.2.txz 

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#3 by Ed_P » 10 Apr 2021, 15:24

My results definitely not the same as yours Bob.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -s thunderbird

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# usm -u all
 Starting slackware database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

Updating config file

 Starting slackwarepatches database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

 Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
 salix  database updated. 

 Starting alien database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting ponce database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 

 Starting slackonly database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackonly  database updated. 

 Starting sbo database update 
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 


Downloading: extra-deps.txt  DONE
Downloading: ignore-deps.txt  DONE

root@porteus:/home/guest# usm -s thunderbird

 Usm is already active. 

If this information is not correct, you can remove the following file and rerun the script:
/var/lock/usm

root@porteus:/home/guest# cat /etc/usm/usm.conf | grep DISTRO
DISTROS="slackware slackwarepatches salix alien ponce slackonly" # slacky

root@porteus:/home/guest# rm /var/lock/usm
rm: cannot remove '/var/lock/usm': No such file or directory
root@porteus:/home/guest# usm -s thunderbird

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# 
:( :%)
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#4 by donald » 10 Apr 2021, 20:38

You're doing it wrong. :) -- just kidding. :)

You will only get this error if you have never updated Slacky before - when it was still working.

Now what?

a) remove slacky from the DISTROS line [/etc/usm/usm.conf] to update the other databases with
usm -u all

b) Add Slacky back to the DISTROS line

c) Open /var/usm/slacky > create CHECKSUMS.md5 , LIBS.TXT , OPTIFEST , PACKAGES.TXT
[empty files will do]

d) search for (whatever)packages usm -s whatever

I still haven't found out where to completely deactivate/remove slacky in/from usm.

Bob1414
Black ninja
Black ninja
Posts: 33
Joined: 28 Mar 2021, 15:35
Distribution: Cinnamon 4 kernel5.11.13 p

restarting USM??

Post#5 by Bob1414 » 11 Apr 2021, 01:07

donald wrote:
10 Apr 2021, 20:38

c) Open /var/usm/slacky > create CHECKSUMS.md5 , LIBS.TXT , OPTIFEST , PACKAGES.TXT
[empty files will do]
Thanks, Donald. I think I see what you're getting at, but it didn't work for me. Tomorrow, I'm going to try again but also make sure to check the contents of all the repo folders. There are certain oddities.
Ed_P wrote:
10 Apr 2021, 15:24
My results definitely not the same as yours Bob.
Ed, when I put the OPTIFEST dummy file into /var/usm/slacky, I ended up with the same error report as you get - about the lock that isn't there. But when I added in a dummy MANIFEST file, I went back to how I'd started: I am presented with 2 Thunderbird files but they won't download.

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#6 by donald » 11 Apr 2021, 03:38

Yup, seems I can't get packages which are flagged "from slackwarepatches"..
Tried with random packages from the /var/usm/slackwarepatches/PACKAGES.TXT file.
( not sure if i ever got one in the past)

Everything else does work.
Databases are updated - no stop because of usm errors - download,fetching dependencies,
building a module, all OK.

e.g. Got sylpheed + dependencies from ponce and/or slackonly,
also claws-mail etc.

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#7 by Ed_P » 11 Apr 2021, 03:48

donald wrote:
10 Apr 2021, 20:38
You will only get this error if you have never updated Slacky before - when it was still working.
I've used USM for years with Porteus 4.0 so pretty sure the files are there. However

Code: Select all

guest@porteus:~$ ls -l /var/usm/slacky
total 40
-rw-r--r-- 1 root root 12680 Mar  8 13:22 CHECKSUMS.md5.gz
-rw-r--r-- 1 root root  2154 Oct  9  2016 LIBS.TXT.gz
-rw-r--r-- 1 root root 12680 Mar  8 13:22 MANIFEST.bz2
-rw-r--r-- 1 root root 12680 Mar  8 13:22 PACKAGES.TXT.gz
guest@porteus:~$ 
apparently not in the right format. :o :%)

I know how to unzip the .gz files but what do I do with the .bz2 one?
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#8 by donald » 11 Apr 2021, 04:44

Ed_P wrote:
11 Apr 2021, 03:48
apparently not in the right format.
The files in /var/usm/slacky should be readable like txt files not *.gz etc.
[ compare them with the files in e.g. /var/usm/slackware/ ]
I know how to unzip the .gz files but what do I do with the .bz2 one?
bzip2 -d MANIFEST.bz2

but you want an OPTIFEST file in the folder.

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#9 by Ed_P » 11 Apr 2021, 05:51

Still not working.

Code: Select all

root@porteus:/home/guest# usm -g thunder

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# usm -u all
slackware was updated 522 seconds ago. Skipping.
slackwarepatches was updated 512 seconds ago. Skipping.
salix was updated 509 seconds ago. Skipping.
alien was updated 503 seconds ago. Skipping.
ponce was updated 499 seconds ago. Skipping.
slackonly was updated 478 seconds ago. Skipping.
sbo was updated 0 seconds ago. Skipping.

extra-deps.txt was updated 476 seconds ago. Skipping.
ignore-deps.txt was updated 476 seconds ago. Skipping.

You can change the time limit for skipping in: /etc/usm/usm.conf
The default is 3 hours
root@porteus:/home/guest# ls -l /var/usm/slacky
total 0
-rw-r--r-- 1 root root 0 Apr 11 01:30 CHECKSUMS.md5
-rw-r--r-- 1 root root 0 Apr 11 01:29 LIBS.TXT
-rw-r--r-- 1 root root 0 Apr 11 01:31 OPTIFEST
-rw-r--r-- 1 root root 0 Apr 11 01:32 PACKAGES.TXT
root@porteus:/home/guest# cat /etc/usm/usm.conf | grep DISTROS
DISTROS="slackware slackwarepatches salix alien ponce slackonly" # slacky
root@porteus:/home/guest# usm -g thunder

 Usm is already active. 

If this information is not correct, you can remove the following file and rerun the script:
/var/lock/usm

root@porteus:/home/guest# rm /var/lock/usm
rm: cannot remove '/var/lock/usm': No such file or directory
root@porteus:/home/guest#  
:hammer:
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#10 by donald » 11 Apr 2021, 10:10

Ed
There is nothing wrong.
This MESSAGE [Usm is already active..and so on] is/was always there after an usm -u all update.

No action like rm /var/lock/usm required.

Simply rerun the search <package> command. [ usm -g thunder in your example ]

EDIT
If you have created the 4 empty files in /var/usm/slacky, you must also add slacky back to the DISTROS line.
The output you posted shows you haven't done that.

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#11 by Ed_P » 11 Apr 2021, 17:58

:crazy: :crazy: :crazy:
donald wrote:
07 Apr 2021, 10:12
Conclusion:
Remove slacky from the DISTROS line -- until there is a working mirror.
If the /var/usm/slacky files are present and slacky is removed from usm.conf USM fails to run.

Restored from a old backup.

Code: Select all

root@porteus:/home/guest# ls -l /var/usm/slacky
total 81
-rw-r--r-- 1 root root 23039 May  5  2019 CHECKSUMS.md5
-rw-r--r-- 1 root root 12227 Jan 29 14:38 LIBS.TXT
-rw-r--r-- 1 root root  4315 Jan 29 14:38 OPTIFEST
-rw-r--r-- 1 root root 42698 May  5  2019 PACKAGES.TXT
root@porteus:/home/guest# 

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -g thunder

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) thunderpad-20150716-x86_64-1_slonly.txz
#? ^C
root@porteus:/home/guest# xed /etc/usm/usm.conf

(xed:1992): dconf-WARNING **: 13:36:33.556: failed to commit changes to dconf: The connection is closed

(xed:1992): dconf-WARNING **: 13:36:33.678: failed to commit changes to dconf: The connection is closed
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

(xed:1992): dconf-WARNING **: 13:36:33.774: failed to commit changes to dconf: The connection is closed

(xed:1992): dconf-WARNING **: 13:36:33.774: failed to commit changes to dconf: The connection is closed

(xed:1992): dconf-WARNING **: 13:36:33.774: failed to commit changes to dconf: The connection is closed

** (xed:1992): WARNING **: 13:36:53.131: Set document metadata failed: Setting attribute metadata::xed-encoding not supported

(xed:1992): dconf-WARNING **: 13:36:55.941: failed to commit changes to dconf: The connection is closed

** (xed:1992): WARNING **: 13:36:55.973: Set document metadata failed: Setting attribute metadata::xed-position not supported
root@porteus:/home/guest# cat /etc/usm/usm.conf | grep DISTROS
DISTROS="slackware slackwarepatches salix alien ponce slackonly"
root@porteus:/home/guest# usm -g thunder

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# 
:wall:
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#12 by donald » 11 Apr 2021, 20:44

Ed...I beg you please,...(logic is required)

a) If you take a stock porteus and run usm -u all, usm fails at slacky no matter which
mirror you chose in /etc/usm/mirrors-slacky.txt because the mirrors don't work at all
or deliver files which are not what they seem to be.
Example:
This is what I got from the slackware.org.uk mirror
root@porteus:/var/usm/slacky# file CHECKSUMS.md5.gz
CHECKSUMS.md5.gz: HTML document, ASCII text, with very long lines
so
b) To make USM to run through the update process of the databases (except slacky)
you have to remove slacky from the DISTROS line.
Now USM will not fail/stop with an error while updating the remaining databases.

If one tries, at this stage, to search for [or get/download] a package/programm
USM still fails because removing slacky from the DISTROS line is not enough to stop
USM asking for slacky repo.
so
c) put slacky back into the DISTROS line and create the 4 files in /var/usm/slacky
( At this point I assume the creation/modification timestamp of those files is
enough to convince USM that they are valid because the files I created had no content.)
now
d) one can use USM as usual
Note: do not run usm -u all again.

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#13 by Ed_P » 11 Apr 2021, 21:57

So, the usm.conf tweak is just for the usm -u all problem! :mega_shok: I think I'll stick to my usmupdates.sh script that I posted here: Save files :happy62: Just switch slacky with slackonly.
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1826
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

restarting USM??

Post#14 by donald » 12 Apr 2021, 00:21

well,well,well...
Have you tried your script with a new installation of porteus (or in always fresh)?
How did it went?

Of course one has to comment out slacky but you also do not get "extra debs".
[and slackwarepatches]

Moreover, if I boot in always fresh mode, all folders in /var/usm/ are empty by default.
That would also be the case for a new porteus user in normal mode.
So one has to put something into /var/usm/slacky to avoid the "missing databases" error,no?

User avatar
Ed_P
Contributor
Contributor
Posts: 6331
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

restarting USM??

Post#15 by Ed_P » 12 Apr 2021, 05:42

:hmmm: So, for a new 4.0 user they:

Modify /etc/usm/usm.conf to remove slacky from the DISTROS line.
Run usm -u all
Run an echo " " > /var/usm/slacky/CHECKSUMS.md5 and repeat for LIBS.TXT, OPTIFEST and PACKAGES.TXT
Modify /etc/usm/usm.conf to readd slacky to the DISTROS line.

And for future usm updates they can run the modified version of my usmupdates.sh script or repeat the above steps.

Yes? :)
Ed

Post Reply