USM bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
rych
Warlord
Warlord
Posts: 622
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

USM bug reports

Post#526 by rych » 15 Nov 2017, 05:41

The safm.sh stumbled too at some stage. I decided to delete /var/usm and /etc/usm, reboot, and start anew. Then usm eventually worked well. But before it did, it presented me with a different BUG:

As it resolves dependencies and downloads archives it doesn't seem to be checking for their integrity, and continues merrily to covert them to modules or bundles, which apparently install fine, except the application is broken. I went to the /tmp/usm and tried to open each archive and yes, one was corrupt.

Not sure if anyone is developing usm currently. For now I've decided that if anything goes wrong at all, any error message, I will be erasing /var/usm, /etc/usm, AND /tmp/usm. Then I must wait for a few days, unfortunately, before trying again. Only when everything looks smooth can I hope to have a successful installation.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

USM bug reports

Post#527 by Ed_P » 15 Nov 2017, 06:17

You will note from the distribution files that there are many mirrors. Some mirrors may have downloaded some corrupted files and some may not have. Using the scripts you have tried helps to get around the damaged mirrors. Starting from scratch repeatedly doesn't seem to be the fastest approach to a solution.
Ed

Jack
Contributor
Contributor
Posts: 1857
Joined: 09 Aug 2013, 14:25
Distribution: Porteus and Nemesis
Location: USA

USM Error

Post#528 by Jack » 28 Nov 2017, 20:15

What cause this error? How can it be fixed?

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u all
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
slackware was updated 477 seconds ago. Skipping.
slackwarepatches was updated 465 seconds ago. Skipping.
slacky was updated 461 seconds ago. Skipping.
salix was updated 445 seconds ago. Skipping.
alien was updated 439 seconds ago. Skipping.
ponce was updated 433 seconds ago. Skipping.
slackonly was updated 379 seconds ago. Skipping.
sbo was updated 268 seconds ago. Skipping.

extra-deps.txt was updated 266 seconds ago. Skipping.
ignore-deps.txt was updated 265 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#
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

USM bug reports

Post#529 by Ed_P » 29 Nov 2017, 00:30

I just ran this on my Cinnamon 3.2.2 system.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u all
slackware was updated 285 seconds ago. Skipping.
slackwarepatches was updated 276 seconds ago. Skipping.
slacky was updated 271 seconds ago. Skipping.
salix was updated 202 seconds ago. Skipping.
alien was updated 260 seconds ago. Skipping.
ponce was updated 254 seconds ago. Skipping.
slackonly was updated 229 seconds ago. Skipping.
sbo was updated 202 seconds ago. Skipping.

extra-deps.txt was updated 202 seconds ago. Skipping.
ignore-deps.txt was updated 202 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 /tmp
total 14576
drwx------ 2 guest users      60 Nov 28 19:23 firefox_guest/
-rw-r--r-- 1 root  root  7462912 Nov 28 19:22 my40changes.xzm
-rw-r--r-- 1 root  root  7462912 Nov 28 19:21 mychanges.xzm
drwx------ 2 guest users      80 Nov 28 19:13 pulse-PKdhtXMmr18n/
drwxr-xr-x 2 root  root       40 Nov 28 19:19 usm/
drwx------ 2 root  root      220 Nov 28 19:24 usm.ml4kcr/
root@porteus:/home/guest# 
 
The permission error doesn't appear to stop the USM update from running and a search of the forum shows it appearing in several of Bogomips postings.

I wonder if it's tied to a virtual machine.
Ed

Post Reply