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: 7675
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.0 ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#256 by Ed_P » 05 Aug 2014, 05:29

Tried the USM GUI Update USM option, was told that I have the current version.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -v

 You are using USM version:  3.1.2

root@porteus:/home/guest# 
I don't think so.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#257 by brokenman » 05 Aug 2014, 14:03

edit to add, by the way that initrd.xz is in a 64 bit folder on your repo, is there a 32 bit one or does it matter?
No you can use this initrd.xz for both architectures. The change made was to fix a problem with a certain whiteout file due to the difference in nature of the changes=EXIT cheatcode. Updating this file (initrd.xz) is the correct procedure for fixing the problem you are experiencing. The latest Porteus release is now out and contains the fix. (see announcement thread)
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#258 by brokenman » 22 Aug 2014, 02:24

+-------------------------
Thu Aug 21 23:03:45 UTC 2014
Fixed module question showing in slackware (thanks Slaxmax)
Fixed deselect option not working in CLI (thanks Slaxmax)
Added database dir to preferences in GUI
Fixed extra-deps being removed in global update (thanks Bogomips)
Removed multiple updates of config file during global update
Add ignored-deps.txt functionality for deps that are not required
Change default time from 24 hours to 3 hours for skipping updates (thanks Ed_P)
Fixed sbo not updating in global update (thanks cttan)
Added openldap-client missing dep for ekiga (thanks cttan)
Fixed dolphin not opening storage folder (thanks router)

+-------------------------
Thu Aug 08 01:39:17 UTC 2014
Fixed bug when package name is doubled (Thanks Tome)

Updated to v3.1.5
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: USM Unified Slackware Package Manager

Post#259 by Ed_P » 22 Aug 2014, 05:53

Porteus 3.0.1
USM 3.1.4

USM GUI - Updates - Update USM: Message "You have the current USM version."

LXTerminal:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -v

 You are using USM version:  3.1.4

root@porteus:/home/guest# usm -u all
 Starting alien database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

Updating config file



Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5591
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: USM Unified Slackware Package Manager

Post#260 by fanthom » 22 Aug 2014, 06:28

@brokenman
a) please add '-v' flag to usm CLI which would show it's version and display it in the help as well (when you run 'usm' with no arguments or with '-h')
b) fix typo:

Code: Select all

nodeps: No dpepndency resolution.
thanks
Please add [Solved] to your thread title if the solution was found.

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#261 by Bogomips » 22 Aug 2014, 12:29

Code: Select all

root@porteus:/home/guest# usm -v

 You are using USM version:  3.1.4

root@porteus:/home/guest# usm -u usm
Downloading: vercheck.txt  DONE

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

 A new version of USM is available.
 Would you like to download it now? [y/n]
Downloading: usm-latest-0.0-noarch-1.txz  DONE
...
  Installing new version now 
usm-latest-0.0-noarch-1:                                                 [310K]

 USM was updated successfully
 You are currently using:
 USM-v3.1.4 
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
fanthom
Moderator Team
Moderator Team
Posts: 5591
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: USM Unified Slackware Package Manager

Post#262 by fanthom » 22 Aug 2014, 13:10

Code: Select all

root@porteus:/home/guest# usm -v

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# 
downloading repo files just to check usm version is a bit of overkill.

besides: '-v' flag should be documented in the usm help.
Please add [Solved] to your thread title if the solution was found.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#263 by brokenman » 22 Aug 2014, 14:24

@Ed_P
It was already established in another thread that this is due to whiteout files. It is not finding your usm.conf file which is clearly there.

@Fanthom
Will do

@Bogomips
Please supply the output of:

Code: Select all

awk -F= '/USMVERSION/{print$NF}' /etc/usm/usm.conf
Anybody else having trouble upgrading? I just tested from three different machines on both archs and could not reproduce this problem.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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#264 by Bogomips » 22 Aug 2014, 15:07

Code: Select all

guest@porteus:~$     awk -F= '/USMVERSION/{print$NF}' /etc/usm/usm.conf
3.1.4
guest@porteus:~$ ls -l /tmp/usm/usm-latest-0.0-noarch-1.txz
-rw-r--r-- 1 root root 61576 Aug  5 04:43 /tmp/usm/usm-latest-0.0-noarch-1.txz
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: 7675
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.0 ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#265 by Ed_P » 22 Aug 2014, 15:23

fanthom wrote:besides: '-v' flag should be documented in the usm help.
So to should the '-u usm' option.
brokenman wrote:@Ed_P
It was already established in another thread that this is due to whiteout files. It is not finding your usm.conf file which is clearly there.
I thought the new initrd file in 3.0.1 was a fix for that. And how does that impact the updating of usm itself? Or, from another point, how do I upgrade to 3.1.5?

Code: Select all

root@porteus:/home/guest# usm -u usm
Downloading: vercheck.txt  DONE

/usr/share/usm/funcupdateDatabase: line 338: [: 140816: unary operator expected
No database updates were found.

/usr/share/usm/funcupdateDatabase: line 351: [: 140821: unary operator expected
You have the current USM version.

root@porteus:/home/guest# 
The update-usm.sh approach seems to be frowned upon. http://forum.porteus.org/viewtopic.php? ... 697#p24697
And I don't see .wh. files that should be effecting this.

Code: Select all

root@porteus:/home/guest# find /mnt/live/memory/changes/etc/usm/ -name .wh.*
/mnt/live/memory/changes/etc/usm/.wh.extra-deps.txt
root@porteus:/home/guest# find /mnt/live/memory/changes/ -name .wh.*
/mnt/live/memory/changes/.wh..wh.orph
/mnt/live/memory/changes/.wh..wh.plnk
/mnt/live/memory/changes/.wh..wh.aufs
/mnt/live/memory/changes/var/log/packages/.wh.usm-3.1.2-noarch-1
/mnt/live/memory/changes/var/log/packages/.wh.usm-3.1.0-noarch-2
/mnt/live/memory/changes/usr/lib64/.wh.libapm.so.1
and

Code: Select all

/mnt/live/memory/changes/etc/usm/.wh.extra-deps.txt
root@porteus:/home/guest# ls /tmp/usm/
root@porteus:/home/guest# 
Last edited by Ed_P on 22 Aug 2014, 15:47, edited 2 times in total.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#266 by brokenman » 22 Aug 2014, 15:36

I have pushed the updates (for version check) to git. I also added extra info to: usm -i or usm info
Aug 5 04:43 /tmp/usm/usm-latest-0.0-noarch-1.txz
Any chance you have a .1 file in /tmp/usm? This bug was addressed in a previous version and all old usm*.txz packages are now removed before downloading of new packages. Will double check now.
So to should the '-u usm' option.
Will do.
I thought the new initrc file in 3.0.1 was a fix for that.
It does address the problem for people that don't already have the problem. All future users of changes=EXIT will not experience the problem. If you already have the problem in your savefile then the linuxrc fix will not help it.
And how does that impact the updating of usm itself?
It doesn't at all. I was referring to the hang you are having when updating databases.
Or, from another point, how do I upgrade to 3.1.5?
You can follow the manual update procedure explained in other threads. Please do this while booted into changes=/path/to/changes.dat and NOT changes=EXIT
Download the usm slackware package and install it using installpkg. I'm not so sure it will even fix your problem but I am hoping that booting with the changes= cheatcode and installing the slackware package will force the files to be seen.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: USM Unified Slackware Package Manager

Post#267 by Ed_P » 22 Aug 2014, 16:04

brokenman wrote:
Or, from another point, how do I upgrade to 3.1.5?
You can follow the manual update procedure explained in other threads. Please do this while booted into changes=/path/to/changes.dat and NOT changes=EXIT
Download the usm slackware package and intall it using installpkg. I'm not so sure it will even fix your problem but I am hoping that booting with the changes= cheatcode and installing the slackware package will force the files to be seen.
And we are cross posting. :( I'm updating my posting while you are adding yours. :o Have you seen my updates?

Something isn't right. I was able to upgrade to 3.1.4 after having problems upgrading to it initially when using 3.0.1, now I'm having problems again. I know how to remove .wh. files from my save.dat file I'm just not sure they are the problem. 98% of them are Firefox and Jave files.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#268 by brokenman » 22 Aug 2014, 16:40

Have you seen my updates?
No. Please add EDIT: when updating previous posts so it is known that they were updated after the original post.
I was able to upgrade to 3.1.4 after having problems upgrading to it initially when using 3.0.1, now I'm having problems again.
Nothing has changed with the update procedure for quite a few versions. The procedure is quite simple. It removes any existing usm-latest-0.0-naorch-1.txz from storage. It downloads the latest usm-latest-0.0-naorch-1.txz file. It installs the usm-latest-0.0-naorch-1.txz file.
The update-usm.sh approach seems to be frowned upon.
I didn't mention anything about using this script. Please follow the instructions in my last post and see if it works. Be sure to boot into changes= and NOT changes=EXIT. Something is certainly screwed up in your changes file and it is near impossible for me to troubleshoot this. I don't know what you have and haven't deleted directly from the savefile and I have recommended not deleting files directly from this file. Delete them from the standard paths and the savefile will take care of itself.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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#269 by Bogomips » 22 Aug 2014, 16:49

brokenman wrote:
Aug 5 04:43 /tmp/usm/usm-latest-0.0-noarch-1.txz
Any chance you have a .1 file in /tmp/usm? This bug was addressed in a previous version

Code: Select all

guest@porteus:~$ sudo find /tmp/usm -regex '.*\.1.*' -maxdepth 1
/tmp/usm/kate-4.10.5
/tmp/usm/at-spi2-atk-2.8.1-i486-1.xzm
/tmp/usm/vlc-qt-0.10.0-i486-1sl.txz
/tmp/usm/aaa_elflibs-14.1
/tmp/usm/at-spi2-atk-2.8.1-i486-1.txz
/tmp/usm/libao-1.1.0
/tmp/usm/vlc-2.1.4
/tmp/usm/libkcddb-4.10.5-i486-1.xzm
/tmp/usm/kde-baseapps-4.10.5
/tmp/usm/kdelibs-4.10.5-i486-2.xzm
/tmp/usm/vlc-2.1.5
/tmp/usm/vlc-2.1.2
brokenman wrote:and all old usm*.txz packages are now removed before downloading of new packages.
Another possibility: old usm*.txz packages removed and old file downloaded?
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
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#270 by brokenman » 22 Aug 2014, 17:08

Another possibility: old usm*.txz packages removed and old file downloaded.
I checked the server file before releasing it. The new one replaces the old one on the server. In your nonstandard setup please give output of: md5sum /etc/usm/usm.conf p10/Por/usm.conf
Essentially I need more people to report if they are having problems with this.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply