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
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#31 by brokenman » 25 Jan 2014, 01:06

@phhpro
USM only supports slackware-14.1 (and slackware-current in the future). Many of your problems no doubt come from the fact that Porteus v2.1 uses slackware-14.0 and as such when usm cross checks your system libs it gets frazzled. This also affects download PATHS since 14.0 is autosensed. Please change the slackware version in /etc/usm/usm.conf which will at least allow you to download the 14.1 database files (and show gimp 2.8.6) but this will still not fix what gets reported as dependencies. In some cases you may get incorrect feedback.

Most slackware managers reside in /sbin or other root only $PATHS but i guess it wouldn't hurt to place a symlink in /usr/bin and do a root check in the script and ask for a password. I'll implement this.

@Francois
Yes i am getting sound from v3.0.
The output you gave showed me a major bug in the way usm is getting links for both salix and ponce. The URL's for the packages are all screwed up. See the double salix/salix in the link? I'll fix this tonight and push another version. I'm sometimes surprise myself how stupid i can be. I had it working nicely and must have changed something in the code. Coding late at night is my only option and well .... enough said.

However, once the slackbuild has been downloaded, usm -rb would be a nice argument to build from the already downloaded file, instead of downloading it anew. What do you think?
Yes absolutely. Thanks. I can add a check to see if the file already exists before downloading again.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: USM Unified Slackware Package Manager

Post#32 by francois » 25 Jan 2014, 02:52

Salut brokenman:
... how stupid i can be ...
:(

Maybe tired and less concentrated would be more appropriate! :)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: USM Unified Slackware Package Manager

Post#33 by francois » 25 Jan 2014, 02:54

Downloading of kaffeine with its many dependencies went just fine. :)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#34 by brokenman » 25 Jan 2014, 03:14

Updated to v3.0.3

+-------------------------
Wed Jan 23 16:52:03 UTC 2014
usm-3.0.3-noarch-1.txz: updated
Fixed bug with getting links from ponce and salix (thanks francois)
Added option to remove files after usm -g (thanks slaxmax)
Added notification if launched as guest (thanks phhpro)
Added option to rebuild slackbuild without redownloading (thanks francois)

Hopefully the above bugs have been fixed. I will give everything a thorough test again on Sunday.
Will add check for slackware-14.0 users to help resolve any confusion.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
phhpro
Full of knowledge
Full of knowledge
Posts: 545
Joined: 10 Nov 2013, 20:35
Distribution: .

Re: USM Unified Slackware Package Manager

Post#35 by phhpro » 25 Jan 2014, 05:27

...
Last edited by phhpro on 04 Feb 2016, 01:38, edited 1 time in total.

User avatar
Slaxmax
Contributor
Contributor
Posts: 403
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: USM Unified Slackware Package Manager

Post#36 by Slaxmax » 25 Jan 2014, 17:48

@brokenman
Deselect an item with 2 digits does not work
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#37 by brokenman » 25 Jan 2014, 18:11

Actually i meant change /etc/usm/usm.conf file to SLACKVER=14.1 (just uncomment the line)

In any case the only difference (for sbo download) here will be the download path. SLACKVER=14.0 means it will download the file from the version 14.0 folder on the slackbuilds repository. I've changed the SLACKVER to 14.0 and 14.1 in the config file and in both cases it successfully downloaded the correct file. You can change line: 583 in /usr/sbin/usm from:

Code: Select all

for a in $FILES; do echo $a; download $REPO_SBO/$SLACKVER/$a $SDIR; done
to

Code: Select all

for a in $FILES; do echo $REPO_SBO/$SLACKVER/$a; download $REPO_SBO/$SLACKVER/$a $SDIR; done
and then run: usm -u sbo to see the exact path it is trying to download from. It should echo:
http://slackbuilds.org/slackbuilds/14.0 ... LDS.TXT.gz if you have SLACKVER=14.0. This is the correct download path. If it doesn't echo this in the terminal then something is wrong.

Francois are you seeing this problem when running usm -u all ?
Does the sbo download fail?

You ought to have a look somewhere around 286 I think it was. helpme???
Thanks. Good catch. I will change this to point to the relevant function. ( I should have called it 'god_help_me' LOL)

Is it me, or why is sbo so different from the rest?
Slackbuilds is indeed different to all the rest. The entire server layout is totally different. They call their index SLACKBUILDS.TXT instead of PACKAGES.TXT (since they don't offer packages) and they don't have a MANIFEST file. This is why (in the code) i have put LEAVEMANIFEST=0 (which tells usm not to process any nonexistent MANIFEST file).

Unfortunately i don't have version 3.0.0 anywhere.

Moreover, the differences between 14.0 and 14.1 are mostly of a minor nature.
For USM the difference will be in the paths it uses to download, the packages offered and the dependencies resolved for a given binary. This last one is pretty major since the libraries (of installed packages) you currently have for slackware-14.0 are being parsed against what is available from slackware 14.1 packages. There is bound to be many inconsistencies and probably unresolved dependencies.

From a user point of view, I wouldn't consider a complete rebuild of all packages against a different version of glibc a minor difference. The GNU C library is kind of important to ALL unices. I guess the developers aim for some kind of backwards compatibility when rewriting libraries but I wouldn't guarantee it.

@Slaxmax. Thanks, it's a shame that i will have to remove the single button touch. User will now have to type the number and press enter.
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: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#38 by brokenman » 25 Jan 2014, 21:00

+-------------------------
Wed Jan 25 18:19:26 UTC 2014
usm-3.0.4-noarch-1.txz: updated
Fixed deselct items when more than 10 (thanks slaxmax)
Fixed lockfile check (thanks phhpro)
Fixed bad check for processing SUPPLIMENT and MANIFEST files.
Removed skype_static from list of mother packages
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: USM Unified Slackware Package Manager

Post#39 by francois » 25 Jan 2014, 21:09

Francois are you seeing this problem when running usm -u all ?
Does the sbo download fail?


I have no problem at all. Every repo are downloaded just fine, including sbo:

Code: Select all

root@porteus:~# usm -u all
Starting sbo database update 
Connection is good
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 

 Starting alien database update 
Connection is good
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 alien  database updated.  
...
Voltaire: Le mieux est l'ennemi du bien.

User avatar
phhpro
Full of knowledge
Full of knowledge
Posts: 545
Joined: 10 Nov 2013, 20:35
Distribution: .

Re: USM Unified Slackware Package Manager

Post#40 by phhpro » 26 Jan 2014, 00:11

...
Last edited by phhpro on 04 Feb 2016, 01:38, edited 1 time in total.

User avatar
phhpro
Full of knowledge
Full of knowledge
Posts: 545
Joined: 10 Nov 2013, 20:35
Distribution: .

Re: USM Unified Slackware Package Manager

Post#41 by phhpro » 26 Jan 2014, 03:26

...
Last edited by phhpro on 04 Feb 2016, 01:34, edited 1 time in total.

User avatar
Slaxmax
Contributor
Contributor
Posts: 403
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: USM Unified Slackware Package Manager

Post#42 by Slaxmax » 26 Jan 2014, 03:49

There is some error download in alien mirror

Code: Select all

Downloading: vlc-2.1.2-i486-3alien.txz  DONE
 There was a problem downloading the file:  vlc-2.1.2-i486-3alien.txz
same error in lua and ffmpeg package
I accessed via browser the mirror and the packages are correct.
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#43 by brokenman » 26 Jan 2014, 04:09

The thing that stands out for me is this:
Binaryfile/var/usm/slackware/PACKAGES.TXTmatches was found in slackware

For some reason the PACKAGES.TXT file (after being gunzipped) is being detected as a binary file when it should be a text file. You can check with: file /var/usm/slackware/PACKAGES.TXT
Please also check the output from: file /var/usm/sbo/SLACKBUILDS.TXT.gz if it is still there.
And also from : gzip --version
When you grep a binary file it returns with this message: matches were found in "filename"

You know, when i was transferring files from sourceforge to my computer and vice versa i ran into this problem. It was a simple README text file that somehow turned binary on me. I've never seen that before. Even stranger because that PACKAGES.TXT file is downloaded from slackware mirrors and only the LIBS.TXT files (and MANIFEST for salix) are downloaded from SF. I'll have to look further in to what could be making the system believe that the file format has changed like that.

That line where the linenumber error changed is simply a long line that i split into two. It sends the function name and line number where the script failed into the error log. Odd that it jumped a line but i think nothing to worry bout.
Are you booting with 'save changes?'

@Slaxmax
I will take a look at the alien repo paths today.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
phhpro
Full of knowledge
Full of knowledge
Posts: 545
Joined: 10 Nov 2013, 20:35
Distribution: .

Re: USM Unified Slackware Package Manager

Post#44 by phhpro » 26 Jan 2014, 05:56

...
Last edited by phhpro on 04 Feb 2016, 01:34, edited 1 time in total.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#45 by brokenman » 26 Jan 2014, 16:37

Yes I believe it is related to wget download mode or the locale environment when trying to read a text file encoded in UTF-8.

For slackware please try opening /etc/usm/mirror-slackware.txt and changing the mirror to some http address. Then repeat the same problem you have above.

What confuses me is that nobody else has this problem, but because i know you know what you are doing i can't let it slide. Have you changed locale settings?
Please supply the output of: echo $LANG

Also once you have successfully updates and the PACKAGES.TXT.gz file has been unpacked please supply the output of: od -x < /var/usm/slackware/PACKAGES.TXT|head -n1
I want to look directly at the dump to see why this file reporting to be binary.

@ Slaxmax there is indeed a problem with alien repo links for 32bit. They call i486 --> x86 in the website heirarchy so i have added an exception and will push the update today or tomorrow.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply