USM Unified Slackware Package Manager

[igreka]

Thanks for the reply Ed,

My Porteus kernel is 3.14.15 and it is running on a DELL Inspiron 640M, dual core, 32 bits.

Attempting usm -u usm results in the following:

Downloading: vercheck.txt DONE

An update is available for the usm database files.
Please run: usm -u all

You have the current USM version.

[Bogomips]

First, as a test, in always fresh mode, without saving changes in /home/guest:

Code: Select all

su
removepkg  usm-latest-0.0-noarch-1

or whatever /var/log/packages has for usm.

Then download the appropriate usm package from SourceForge link to /home/guest, then

Code: Select all

installpkg  usm-latest-0.0-noarch-1

if that is the package name.

Good luck.

[igreka]

It doesn't seem to work.

The removepkg seems to work fine as it make 'usm' inaccessible.

But the installpkg does not bring back the 'usm' command, even though it was that the package was installed.

[Bogomips]

Been a while since I last done something like this. Could be something to do with whiteouts, but don't think so. And nothing given for

Code: Select all

which usm
file /usr/bin/usm
file /opt/porteus-scripts/usm

[igreka]

Interestingly, which usm results in /usr/bin/usm

file /usr/bin/usm outputs /usr/bin/usm: Bourne-Again shell script, ASCII text executable

There is no usm script in /opt/porteus-scripts/

[Bogomips]

Code: Select all

su
which usm
file /usr/bin/usm
ls -l /usr/bin/usm
usm -v
/usr/bin/usm -v

[Ed_P]

Maybe this brokenman script will help rebuild the USM system.

http://forum.porteus.org/viewtopic.php? ... 697#p24697

[igreka]

Wow, thanks Ed.

The Brokenman script worked like a charm and did upgrade usm to the latest version as expected.

The repo updates work fine now including the sbo database. fantastic.

Thank you all for your inputs.

[francois]

Sorry to revive that old thread. What would be the more recent one on usm and errors or bugs?

[Ed_P]

http://forum.porteus.org/viewtopic.php?f=39&t=7000

1. sesm.sh

Script to Set the fastest Slackware Mirrors


2. safm.sh

Script to Set Alternative Fastest Mirror

[francois]

Maybe we should start one explaining a few common solution to usm errors:
1) the salix database error (is it fixed for porteus 4.0?)
2) One or more errors occurred while usm was running:

FATAL ERROR!
resolve_deps 369
Please wait 6 hours for the next database update. Could not find: LIBS.TXT

And other common errors encountered. Would we have enough material for that?

[Ed_P]

Most of the USM distributions have multiple mirrors. Just because one mirror is bad doesn't mean they all are. Have you tried other mirrors?

[francois]

Are you talking about 1) the salix problem or 2) the One or more errors occurred while usm was running?

Personnaly, I have fixed 1) the salix database error by choosing another server and saved it in/porteus/rootcopy/etc/usm/mirrors-salix.txt. The rootcopy contains many of my fixes that will survive the porteus release candidate changes and even could be used for nemesis (autostart applications for example).

However, I was wondering if usm would run with minima snags. Or at least that we would have some kind of common problems and solution for usm.

[francois]

2) One or more errors occurred while usm was running:

FATAL ERROR!
resolve_deps 369

I am trying to build qt4.8.7 for smplayer.

Would be solved by changing mirrors

[francois]

Real funny, qt-4.8 from usm tried to pull so much dependencies. When I download it from pkgs.org and txz2xzm, it turns to be the only dependency needed for smplayer.