Porteus

maybe ... Try in a few hours. Or do this: move these files to: (maybe sda1 or sdc1 instead sdb1).

It's the old 2.3.1 version that do not work properly anymore. Only 4.x and abore are ok! Why USM from teminal show 2.3.1, while USM gui 3.7.1.0 ?!?

However the problem is not resolved...

Yes, it’s really old ... Sorry, I don’t know ... You need an advanced guru who will rewrite the slackbuild-file for the new version of MEGAsync and build it from source codes (or convert deb2txz) ...

I think that usm works at best for 4.0 porteus version. Quite sure it has been upgraded for 5.0 rc I will verify and come back on that soon.
Thanks for your patience.

There are issues with usm on porteus 5.0. You will have to work with another package manager sorry. I imagine this will be sorted out after porteus 5.0 official release.

Sorry.

dZ0TFR wrote: ↑

03 Feb 2020, 16:16

Update usm:

Code: Select all

usm -u usm

Update mirrors:

Code: Select all

usm -u all

if it doesn’t work, try this:

Code: Select all

usm -u slacky
usm -u salix
usm -u alien
usm -u ponce
usm -u slackonly
usm -u sbo
usm -u slackware
usm -u slackwarepatches

francois wrote: ↑

09 Feb 2020, 01:40

There are issues with usm on porteus 5.0. You will have to work with another package manager sorry. I imagine this will be sorted out after porteus 5.0 official release.
Sorry.

I'm using 4.0 after experiencing this on 5.0, but I'm having this LIBS.TXT problem just the same. All USM updates work fine either individually or in bulk. It's got something to do with Slackonly.

On another note, I am also getting the "permission denied" error this user is getting, although the updates work just fine once I fix the Slacky mirror.

tagtgren wrote: ↑

26 Aug 2019, 04:30

Sorry for the belated reply, but the issue persists. After running that script and finally running

usm -u all

as root and spending like 50 minutes, terminal has stuck in this

root@porteus:/home/guest# usm -u all
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
Starting slackware database update

Forgive the newbie questions, but why can't I just sudo usm -u all? It seems like it won't let me do anything like this, I have to su root. Am I doing it wrong?

might not work at present because of COVID-19 epidemy in Italy. The answer was here from brokenman USM Unified Slackware Package Manager

Change the repo in the /etc/usm/mirrors-slacky.txt
from EUROPE to UNITED KINGDOM

Add ## in front of the first one:
http://repository.slacky.eu/
Remove ## in front of
http://slackware.org.uk/slacky

If you have some time issues before being able to run

Look into the usm.conf file for time limit and change temporarily 10800 for 10 seconds.

hi, alwaysfunk take a look at this link: https://dslackw.gitlab.io/slpkg/ try it

Hello there beny. How are you doing? I really hope you and your relatives and friends are doing fine.

Do you live in the north or in the south?

hi francois yes we are fine.but you know panta rei so we can't move from home,and yes i live in emilia, north, we are on the red zone....and this too will pass...
so you have to try slpkg isn't simple like usm but maybe is usefull.

With the modification in post 83 usm works fine for me.

Hey there,
I hope you are all fine.
How come I mostly face this error:
p.s: waiting 6hrs is not the cure! Honestly I am not using USM and resolve dependencies one by one by downloading from pkgs.org for ages, but how long?
I really appreciate if anyone at least edit slonly dead Europa mirror on most common .iso files.

S4m4n wrote: ↑

07 Apr 2020, 04:48

I really appreciate if anyone at least edit slonly dead Europa mirror on most common .iso files.

It could be fixed if one would remove slonly from usm, which is possible since it is a mere script.

Then again, for doing so you need to have basic scripting abilities which most do not have.

Rava wrote: ↑

07 Apr 2020, 05:40

Then again, for doing so you need to have basic scripting abilities which most do not have.

looking back few years ago when I didnt know about linux and slax motivated me to learn. I think i can figure it out but dont know what to do ? Now I am on Porteus 4 Mate (5.0rc1 was buggy and I couldn't rely on) I may have chance to try your prescription

S4*:

Have you tried what I did propose in post 83?