USM bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: USM bug reports

Post#256 by tome » 02 Feb 2015, 20:26

I try to understand you, maybe you mix DBDIR and STORAGE, it is not the same. Try in Always Fresh Mode. I will share in the near future my DE-module that is independent from mount point (USM).

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#257 by ElectriQT » 02 Feb 2015, 20:39

me?

Edit:
2 differnet drives appear in my usm-file,
one is from and older installation
and I guess this one should also change when usm changes the "STORAGE=" place . But did not.

DBDIR=/mnt/sdc1/usmsaker
- this is old, leftower from some old experiment, should also change as below :

# Where packages will be downloaded to.
STORAGE=/mnt/sdb1/usm
- this have been updated correct by usm GUI


Thanx
Last edited by ElectriQT on 02 Feb 2015, 20:45, edited 1 time in total.

tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: USM bug reports

Post#258 by tome » 02 Feb 2015, 20:40

Yes, you.
Try manually edit '/etc/usm/usm.conf'.

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#259 by ElectriQT » 02 Feb 2015, 21:18

if we store in user/usm, will it be independent then?

After a change with the GUI to "/root/usm/" it looks like this:

Code: Select all

# usm.conf - Configuration for Unified Slackware Manager (usm)
#

# Resolve dependencies for all packages
# Set this to true or false (never uncomment this)
RESOLVE=true

# The automatice update check that is made when internet
# is accessed. This update check doubles as a check that
# you have internet access before downloading packages.
# Set to false to disable update check.
AUTOCHECK=true

# Storage of database files (e.g PACKAGES.TXT)
DBDIR=/mnt/sdb1/usm/local

# usm works with the repositories of various slackware based distros.
# The variable below is used to find the mirror for each distro given.
# The mirror files are stored in ${DBDIR}/mirrors-distro.txt
DISTROS="slackware slackwarepatches slacky salix alien ponce"

# Where packages will be downloaded to.
STORAGE=/root/usm

# Time before system dependency cache is deleted.
# This is found in function system_deps()
declare -i HOURS=4

# The directory where your slackbuilds source files
# will be downloaded when building from source
SBOTMP=/tmp/usmsbo

# USM uses wget to fetch packages and database updates.
# Uncomment this and put your proxy address here.
#PROXY=http://180.241.124.57:8080

# If your proxy has a username, uncomment it and place it here.
# This setting requires the above #PROXY to be uncommented.
#PROXYUSER=username

# Proxy password
# This setting requires the above #PROXY to be uncommented.
# This setting requires the above #PROXYUSER to be uncommented.
#PROXYPASS=mypassword

# The initial size of the bottom text box window in the GUI
TXTBOX=210

# Do not show any prompts.
# For the GUI this means the last prompt that asks if you want to
# open the folder for viewing will not be shown.
# For the CLI this means just download the packages to storage without
# asking about creating subfolders, etc.
# false means you WILL receive prompts.
NOPROMPTS=false

############ CLI PROMPTS
# CLI option that automatically prompts to
# create a subfolder with name of chosen module
# all dependencies will be downloaded to this subfolder
# This is called from funcpackagesGet
# This variable should be true if you want to be prompted
SUBFOLDERPROMPT=true

############ PORTEUS ONLY SETTINGS

# Convert all slackware packages that are downloaded
# to porteus modules.
MODULES=true

# Merge downloaded packages into one module bundle
MERGE=false

################################
# DO NOT EDIT BELOW THIS POINT
# OR A PUPPY DOG COULD DIE!
################################

# Uncomment and set this value to overide automated detection
# Used for development and troubleshooting only
# ARCH=x86_64

# Uncomment and set this value to overide automated detection
# Used for development and troubleshooting only
#SLACKVER=14.1

USMVERSION=3.1.4
VALIDVERS="14.1 slackware-current"
SUPPLIMENTOPTI=/etc/usm/suppliment-optifest.txt
SUPPLIMENTLIBS=/etc/usm/suppliment-libs.txt
CACHEPATH=/var/cache/usm
CACHE=${CACHEPATH}/usm-cache
CHECKED=$CACHEPATH/checked
USMVER=150127
DBVER=150127
UPDLINK=http://downloads.sourceforge.net/project/usm
DISFILES=$CONFDIR/files.conf
WGETFLAGS="--passive-ftp --trust-server-names --no-check-certificate --progress=dot"
CURLFLAGS=""

PREFIX=/usr

I then manually edit the file to also # Storage of database files (e.g PACKAGES.TXT) DBDIR=/root/usm
Reboot usm,
Update all,
now all the new database files downloads to DBDIR=/root/usm as expected
Search for glibc, =it finds nothing
And then reboot usm again,
..now it Works.

i guess this will add about 130+ MB to my save changes module, but that is ok
In a few months or so I can try to reboot my system :-)
and then we know if it works without mount points , sd*/ as it is now replaced by /root/usm , and If I understand Linuxes filesystem(i dont..) it will follow me in my changes-files now, so it will not depend on what flashSticks / mount point we are at for the moment. Is that Correct?

After my "hack":

Code: Select all

# usm.conf - Configuration for Unified Slackware Manager (usm)
#

# Resolve dependencies for all packages
# Set this to true or false (never uncomment this)
RESOLVE=true

# The automatice update check that is made when internet
# is accessed. This update check doubles as a check that
# you have internet access before downloading packages.
# Set to false to disable update check.
AUTOCHECK=true

# Storage of database files (e.g PACKAGES.TXT)
DBDIR=/root/usm

# usm works with the repositories of various slackware based distros.
# The variable below is used to find the mirror for each distro given.
# The mirror files are stored in ${DBDIR}/mirrors-distro.txt
DISTROS="slackware slackwarepatches slacky salix alien ponce"

# Where packages will be downloaded to.
STORAGE=/root/usm

# Time before system dependency cache is deleted.
# This is found in function system_deps()
declare -i HOURS=4

# The directory where your slackbuilds source files
# will be downloaded when building from source
SBOTMP=/tmp/usmsbo

# USM uses wget to fetch packages and database updates.
# Uncomment this and put your proxy address here.
#PROXY=http://180.241.124.57:8080

# If your proxy has a username, uncomment it and place it here.
# This setting requires the above #PROXY to be uncommented.
#PROXYUSER=username

# Proxy password
# This setting requires the above #PROXY to be uncommented.
# This setting requires the above #PROXYUSER to be uncommented.
#PROXYPASS=mypassword

# The initial size of the bottom text box window in the GUI
TXTBOX=210

# Do not show any prompts.
# For the GUI this means the last prompt that asks if you want to
# open the folder for viewing will not be shown.
# For the CLI this means just download the packages to storage without
# asking about creating subfolders, etc.
# false means you WILL receive prompts.
NOPROMPTS=false

############ CLI PROMPTS
# CLI option that automatically prompts to
# create a subfolder with name of chosen module
# all dependencies will be downloaded to this subfolder
# This is called from funcpackagesGet
# This variable should be true if you want to be prompted
SUBFOLDERPROMPT=true

############ PORTEUS ONLY SETTINGS

# Convert all slackware packages that are downloaded
# to porteus modules.
MODULES=true

# Merge downloaded packages into one module bundle
MERGE=false

################################
# DO NOT EDIT BELOW THIS POINT
# OR A PUPPY DOG COULD DIE!
################################

# Uncomment and set this value to overide automated detection
# Used for development and troubleshooting only
# ARCH=x86_64

# Uncomment and set this value to overide automated detection
# Used for development and troubleshooting only
#SLACKVER=14.1

USMVERSION=3.1.4
VALIDVERS="14.1 slackware-current"
SUPPLIMENTOPTI=/etc/usm/suppliment-optifest.txt
SUPPLIMENTLIBS=/etc/usm/suppliment-libs.txt
CACHEPATH=/var/cache/usm
CACHE=${CACHEPATH}/usm-cache
CHECKED=$CACHEPATH/checked
USMVER=150127
DBVER=150127
UPDLINK=http://downloads.sourceforge.net/project/usm
DISFILES=$CONFDIR/files.conf
WGETFLAGS="--passive-ftp --trust-server-names --no-check-certificate --progress=dot"
CURLFLAGS=""

PREFIX=/usr

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 bug reports

Post#260 by brokenman » 03 Feb 2015, 00:32

Yes using changes will mean you can leave it in /root/usm. Be aware though that the DBDIR (database directory) is where the database is downloaded to. The STORAGE variable is where your newly download packages will land. If I understand correctly your main problem was that you changed the DBDIR variable using the GUI and it didn't update the usm.conf file correctly?

There are no caches or anything like that when it comes to reading storage variables. It reads directly from usm.conf.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: USM bug reports

Post#261 by Ed_P » 03 Feb 2015, 03:02

ElectriQT wrote:i guess this will add about 130+ MB to my save changes module, but that is ok
FWIW This is the space used by USM in my savedat file.

Code: Select all

96K	/mnt/live/memory/images/changes/etc/usm
ls /mnt/live/memory/images/changes/etc/usm
extra-deps.txt	   mirrors-salix.txt		 mirrors-slacky.txt
files.conf	   mirrors-sbo.txt		 suppliment-libs.txt
ignore-deps.txt    mirrors-slackverse.txt	 suppliment-optifest.txt
mirrors-alien.txt  mirrors-slackware.txt	 usm.conf
mirrors-ponce.txt  mirrors-slackwarepatches.txt  version.txt

2.6M	/mnt/live/memory/images/changes/var/log
6.3M	/mnt/live/memory/images/changes/var/usm
432K	/mnt/live/memory/images/changes/var/usm/alien
224K	/mnt/live/memory/images/changes/var/usm/local
604K	/mnt/live/memory/images/changes/var/usm/ponce
704K	/mnt/live/memory/images/changes/var/usm/salix
2.4M	/mnt/live/memory/images/changes/var/usm/sbo
1.4M	/mnt/live/memory/images/changes/var/usm/slackware
152K	/mnt/live/memory/images/changes/var/usm/slackwarepatches
576K	/mnt/live/memory/images/changes/var/usm/slacky
Ed

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

Re: USM bug reports

Post#262 by Ed_P » 03 Feb 2015, 03:14

When I update USM, via the GUI I get this:

Code: Select all

sh-4.2# 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

 Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
 salix  database updated. 

Updating config file

 Starting slacky database update 
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
 slacky  database updated. 

Updating config file

 Starting ponce database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 

Updating config file

 Starting slackware database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

Updating config file

 Starting slackwarepatches database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

Updating config file

 Starting sbo database update 
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 

Updating config file


Downloading: extra-deps.txt  DONE
Downloading: ignore-deps.txt  DONE

 You can now close this window 


sh-4.2# 
When I close the terminal window and recycle USM then search for "flash" and click on
"flashplayer-plugin-11.2.202.440-x86_64-1alien.txz" I get:
Fatal error

LIBS.TXT
Processing:

Brokenman needs to update database. Could not find: LIBS.TXT
Fix please.
Ed

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#263 by ElectriQT » 03 Feb 2015, 10:16

Ed_P wrote:When I update USM, via the GUI I get this:

Code: Select all

...
 Starting slackwarepatches database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

Updating config file

 Starting sbo database update 
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 

Updating config file


Downloading: extra-deps.txt  DONE
Downloading: ignore-deps.txt  DONE

 You can now close this window 


sh-4.2# 
When I close the terminal window and recycle USM then search for "flash" and click on
"flashplayer-plugin-11.2.202.440-x86_64-1alien.txz" I get:
Fatal error

LIBS.TXT
Processing:

Brokenman needs to update database. Could not find: LIBS.TXT
Fix please.

I had exactly the same problems before I changed the database storage to /root/usm , now it seems to work
at least for firefox
I updated manually

Im am not Linux-guy, so Im not 100% sure this is the correct way to do it, but I did download manually and rightclick "convert to .xzm"
then I saved a backup of my bookmarks and stuff in firefox, menu, "Bookmarks" > "show all bookmarks" > "Import and Backup" > probably smart to use the json-files also, I only did an htmlbackup, so I lost my browsing history when updating firefox. Probably possible to fix that too, if I change someting i Profiles/blabla , but I dont know Firefox / Porteus good enough yet.

So if USM dont work, might you want to try this way and download manually ?

(and I hope 14.1 is correct version now , is it ? and not the Slackware "Current". Or? here is all, 32 and 64:
http://mirrors.slackware.com/slackware/ )


So for Firefox 64bit, I assume that would be,(today..):
http://mirrors.slackware.com/slackware/ ... ck14.1.txz
( and in the future when next update come, here: http://mirrors.slackware.com/slackware/ ... /packages/ )

32bit:
http://mirrors.slackware.com/slackware/ ... /packages/
http://mirrors.slackware.com/slackware/ ... ck14.1.txz

Please backup your bookmarks and stuff first from Firefox
right click, make .xzm of the new downloaded firefox,
rename the new one to the same name as your old firefox have in you porteus/base folder now, (in my case here it was at my sda-drive) /mnt/sda1/porteus/base/04-firefox.xzm)
Deactivare(right click) and Move the old firefox from you "porteus/base" folder to a backup folder ..if someting goes wrong. (move it somewhere outside Porteus folders, guest/desktop or whatever)

Move in the new one, activate.
(Firefox will be to find in the ["internet"] menu now)

(This is slackware, not a porteus Firefox-module, so duckDuckGo and special things like that will not be there, I dont know how to do a porteus-compatible one, so "we" get the search-money from duckduck to the Porteus-project again)

Ed_P, did you also update Flashplayer ok now, to Version .440?

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#264 by ElectriQT » 03 Feb 2015, 11:02

Ed_P wrote:
ElectriQT wrote:i guess this will add about 130+ MB to my save changes module, but that is ok
FWIW This is the space used by USM in my savedat file.

Code: Select all

96K	/mnt/live/memory/images/changes/etc/usm
ls /mnt/live/memory/images/changes/etc/usm
[..]
1.4M	/mnt/live/memory/images/changes/var/usm/slackware
152K	/mnt/live/memory/images/changes/var/usm/slackwarepatches
576K	/mnt/live/memory/images/changes/var/usm/slacky
Ed_P
Please Check again.

just the MANIFEST file if we look in the slackwarepatches folder is 55-57MB !

(@Brokenman, idéa for USM:
In the future development, We could have a choice to use compressed files in USM also, as an alternative?
The size on our disk for Porteus session save-modules for this part would go down to about only 10% in the "manifests" if we use tar.gz! Then we can save them in our local storage place and have no problem with changing mount-points when moving flash sticks between different computers any more. And tar.gz seems to be "Ok" in compression, and one of the fastest.

I Tested this now, on slackwarepatches/Manifest 55MB on disk, (57MB)
= only 5.2 MB compressed, and it only took about 2 seconds extra to compress, probably even faster to read/decompress.

Do you like it this idea? )

[Edit: on my 2009 laptop, loaded to 100% at one core and to 40% at the other, Then I started a test compress with tar.gz of the full downloaded usm database folder (133MB on disk) , it took 6-8 seconds to deliver a new compressed file, but now it is only 13.6 MB! That Would be a Perfect size for our storage when we have very slow flash writes and no hdd, I would like this size in my Porteus changes-module compared to the bloathy 133 extra MB now.. :-) , a full Decompress took only 1-2 seconds of the 133MB and all structures there. Will be even faster when the computer is not busy working with a lot of other tings.. hehe )

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

Re: USM bug reports

Post#265 by Ed_P » 03 Feb 2015, 16:35

ElectriQT wrote:I had exactly the same problems before I changed the database storage to /root/usm , now it seems to work
.....

So if USM dont work, might you want to try this way and download manually ?
Thanks ElectricQT but I rather have USM work, as designed. Image The module giving me the trouble is the Flash 440 one.
Ed

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#266 by ElectriQT » 03 Feb 2015, 16:47

Ah, of course, but I cant wait. So I have to learn more about Linux and fix it my self. :-)

I just downloaded Flashpalyer from the web and made a module instead,as it is so critical for me to have that one safe, could not wait.

then I put flashplayer in "modules" folder and activated it.

( Hmm, but did your glibc-bugfix work in USM now, but not flash??
Or maybe that is your next step to update now. )

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#267 by ElectriQT » 03 Feb 2015, 16:53

Ed_P wrote:When I update USM, via the GUI I get this:

When I close the terminal window and recycle USM then search for "flash" and click on
"flashplayer-plugin-11.2.202.440-x86_64-1alien.txz" I get:
Fatal error

LIBS.TXT
Processing:

Brokenman needs to update database. Could not find: LIBS.TXT
Fix please.

I still had this error now, for the glibc-bugpatch downloads
I temporary "fixed" it by unchecked the box [Resolve dependencie] Then it did work, for this file, (as I assume I already have all needed other files in THIS case. But still dont know what the USM-error was about.)

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#268 by ElectriQT » 03 Feb 2015, 17:12

Ed_P wrote:
ElectriQT wrote:I had exactly the same problems before I changed the database storage to /root/usm , now it seems to work
.....

So if USM dont work, you might you want to try this anyway and download manually ?
Thanks ElectricQT but I rather have USM work, as designed. Image The module giving me the trouble is the Flash 440 one.
http://www.slackware.com/~alien/slackbu ... /pkg/14.1/ Try this if you cant get usm to work,
Save, rightclick and convert it to an .xzm module,
Move it to Porteus/modules folder, rightclick "activate",


Then Check at Adobes site that you really are runing the latest player now! (today it is version .440)

if needed you can try to reboot your session without a complete restart of the computer, ,
ctrl+del+backspace, kills the current session, flush(clear?) memory, and restart processes that might have a high cpu load for some bug-reason.,

(and you use you GUEST passwd. in the login screen to get back, save all yor active work first, or it will be lost.. But Firefox most of the time will restore all the tabs that you had open.)

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM bug reports

Post#269 by Bogomips » 03 Feb 2015, 22:32

USM Update Crash

Code: Select all

 usm -u all
...
Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE

gzip: /var/usm/salix/OPTIFEST.gz: unexpected end of file
          

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:                       
 
FATAL ERROR!
usm update_database 264
Could not decompress: OPTIFEST.gz
 
============================================================================== 
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

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#270 by ElectriQT » 03 Feb 2015, 22:49

Bogomips wrote:USM Update Crash

Code: Select all

 usm -u all

FATAL ERROR!
usm update_database 264
Could not decompress: OPTIFEST.gz
 
Never seen that, but on the other hand..I have not seen much yet. :-)

Do you have enough space left on the device or RAM memory?
Did you try again after a new session restart?

Post Reply