USM Unified Slackware Package Manager

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
User avatar
Ed_P
Contributor
Contributor
Posts: 3929
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#376 by Ed_P » 12 Jul 2016, 03:26

What version of Porteus are you running? And what desktop?

What happens when you run the usm command francois posted above your post?
Ed

igreka
White ninja
White ninja
Posts: 29
Joined: 05 Oct 2014, 21:48
Distribution: porteus 3
Location: lincoln

Re: USM Unified Slackware Package Manager

Post#377 by igreka » 12 Jul 2016, 11:02

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
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#378 by Bogomips » 12 Jul 2016, 11:43

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.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

igreka
White ninja
White ninja
Posts: 29
Joined: 05 Oct 2014, 21:48
Distribution: porteus 3
Location: lincoln

Re: USM Unified Slackware Package Manager

Post#379 by igreka » 13 Jul 2016, 10:49

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
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#380 by Bogomips » 13 Jul 2016, 11:09

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
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

igreka
White ninja
White ninja
Posts: 29
Joined: 05 Oct 2014, 21:48
Distribution: porteus 3
Location: lincoln

Re: USM Unified Slackware Package Manager

Post#381 by igreka » 13 Jul 2016, 14:06

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
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#382 by Bogomips » 13 Jul 2016, 16:38

Code: Select all

su
which usm
file /usr/bin/usm
ls -l /usr/bin/usm
usm -v
/usr/bin/usm -v
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3929
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#383 by Ed_P » 13 Jul 2016, 21:01

Maybe this brokenman script will help rebuild the USM system.

viewtopic.php?f=75&t=3040&p=24697#p24697
Ed

igreka
White ninja
White ninja
Posts: 29
Joined: 05 Oct 2014, 21:48
Distribution: porteus 3
Location: lincoln

Re: USM Unified Slackware Package Manager

Post#384 by igreka » 14 Jul 2016, 12:50

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. :Yahoo!:

Thank you all for your inputs.

User avatar
francois
Contributor
Contributor
Posts: 5356
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

USM Unified Slackware Package Manager

Post#385 by francois » 16 Feb 2018, 19:05

Sorry to revive that old thread. What would be the more recent one on usm and errors or bugs?
Prendre son temps, profiter de celui qui passe.

User avatar
Ed_P
Contributor
Contributor
Posts: 3929
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

USM Unified Slackware Package Manager

Post#386 by Ed_P » 16 Feb 2018, 19:17

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
Ed

User avatar
francois
Contributor
Contributor
Posts: 5356
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

USM Unified Slackware Package Manager

Post#387 by francois » 16 Feb 2018, 19:41

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?
Prendre son temps, profiter de celui qui passe.

User avatar
Ed_P
Contributor
Contributor
Posts: 3929
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

USM Unified Slackware Package Manager

Post#388 by Ed_P » 16 Feb 2018, 21:33

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?
Ed

User avatar
francois
Contributor
Contributor
Posts: 5356
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

USM Unified Slackware Package Manager

Post#389 by francois » 16 Feb 2018, 23:42

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.
Prendre son temps, profiter de celui qui passe.

User avatar
francois
Contributor
Contributor
Posts: 5356
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

USM Unified Slackware Package Manager

Post#390 by francois » 17 Feb 2018, 01:33

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
Prendre son temps, profiter de celui qui passe.

Post Reply