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
francois
Contributor
Contributor
Posts: 6435
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#361 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: 8425
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

USM Unified Slackware Package Manager

Post#362 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: 6435
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#363 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: 8425
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

USM Unified Slackware Package Manager

Post#364 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: 6435
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#365 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: 6435
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#366 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.

User avatar
francois
Contributor
Contributor
Posts: 6435
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#367 by francois » 17 Feb 2018, 01:43

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

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

USM Unified Slackware Package Manager

Post#368 by Ed_P » 17 Feb 2018, 02:22

francois wrote:
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?
1) and hopefully it's fix fixes 2)
Personnaly, I have fixed 1) the salix database error by choosing another server and saved it in/porteus/rootcopy/etc/usm/mirrors-salix.txt.
Yup, doing it manually or using one of bogomips's script will accomplish that.

My USM changes, /etc/usm/* & /var/usm/ will survive also as I have them saved in a module I make of my changes.
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.
There was a script that bogomips had that did fix a lot of the USM errors, unfortunately I don't recall it's name or location at this point. :(
Ed

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

USM Unified Slackware Package Manager

Post#369 by jssouza » 18 Feb 2018, 15:54

francois wrote:
17 Feb 2018, 01:43
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. :roll:
francois, smplayer can be built with qt5 as well. Were you using kde5?

User avatar
francois
Contributor
Contributor
Posts: 6435
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#370 by francois » 18 Feb 2018, 23:21

Good to know. No I was on xfce4. This means that smplayer alone could run on kde5.
Thanks.
Prendre son temps, profiter de celui qui passe.

Post Reply