USM bug reports

[brokenman]

1) I don't see the conundrum here. As stated earlier, ignore the error message, it will be fixed in a day or two.

2) Looks like alien updated vlc a couple of days ago on the repo and I havn't updated the database since. Will do it now. Thanks.

3) This looks normal. You chose vlc-qt and that's what you got. What exactly did you expect the result to be? I can do things like add VLC or QT as a requisite when someone chooses vlc-qt.

EDIT: Pushed update to database and application v3.1.4. Please update USM then update datatabase and try again. Hopefully everything is better.

[Ed_P]

3.0.1 RazorQT ISO

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# 

[Bogomips]

• Code: Select all

   USM was updated successfully
   You are currently using:
   USM-v3.1.4 
  
  root@porteus:/home/guest# cp p10/Por/usm.conf /etc/usm        
  root@porteus:/home/guest# usm -u all
  alien was already updated today. Skipping.
  salix was already updated today. Skipping.
  slacky was already updated today. Skipping.
  ponce was already updated today. Skipping.
  slackware was already updated today. Skipping.
  slackwarepatches was already updated today. Skipping.
  
  Downloading: extra-deps.txt  DONE
  

• Still get FATAL ERROR!

  Code: Select all

  Processing:   samba-4.1.11-i486-1_slack14.1.txz 
            
  
  ==============================================================================
  WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
  ==============================================================================
  One or more errors occurred while usm was running:                       
   
  FATAL ERROR!
   resolve_deps 382
  Could not find: LIBS.TXT
   
  ============================================================================== 
  

[Ed_P]

And in Always Fresh mode we have:

3.0.1 RazorQT ISO

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# 

So what part(s) of save.dat need to be deleted to allow 3.1.4 to dominate? If I do a update-usm.sh that puts everything in my save.dat file but I suspect I only need the /var/usm/ part there.

With a minor bug fix release I wasn't expecting a need to start with a new save.dat file like one one would do with a major new release.

[brokenman]

And in Always Fresh mode we have:
You are using USM version: 3.1.4

Correct. That is how it was released.

So what part(s) of save.dat need to be deleted to allow 3.1.4 to dominate?

I suspect none. Have you tried updating USM?

If I do a update-usm.sh that puts everything in my save.dat file but I suspect I only need the /var/usm/ part there.

update-usm.sh does not exist in Porteus.

With a minor bug fix release I wasn't expecting a need to start with a new save.dat file like one one would do with a major new release.

Frankly I am not sure of the state of your save.dat file so I can't comment, but if you just want to update USM then try updating it.

Bogomips, I just downloaded the latest Porteus-v3.0.1 KDE 32bit and ran the same commands.

Code: Select all

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

 You are using USM version:  3.1.4

root@porteus:/home/guest# usm -g samba

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) samba-4.1.0-i486-2.txz
2) samba-4.1.11-i486-1_slack14.1.txz
#? 2

...... lots of processing .......

The following packages are required. 
cups-1.5.4-i486-3.txz [1856K]
gc-7.4.0-i486-1sl.txz [193K]
gnutls-3.1.25-i486-1_slack14.1.txz [1984K]
guile-2.0.9-i486-1.txz [3060K]
libaio-0.3.109-i486-1.txz [16K]
libtasn1-3.6-i486-1_slack14.1.txz [120K]
libtool-2.4.2-i486-2.txz [416K]
libunistring-0.9.3-i486-1.txz [400K]
p11-kit-0.16.4-i486-1.txz [144K]
python-2.7.5-i486-1.txz [11764K]
samba-4.1.11-i486-1_slack14.1.txz [9844K]
tcl-8.6.1-i486-1.txz [2480K]
tk-8.6.1-i486-1.txz [1684K]

Total size: 33 MB

 Multiple packages were detected.
 Would you like to merge the packages into one module? [y/n]

Can you think of any differences that might allow me to further troubleshoot?
You can bypass the 24hour update thing by an individual manual update: usm -u slackware

It also correctly resolved dependencies for the latest vlc.

[Ed_P]

So what part(s) of save.dat need to be deleted to allow 3.1.4 to dominate?

I suspect none. Have you tried updating USM?

Yes. To which USM says I am already current.

If I do a update-usm.sh that puts everything in my save.dat file but I suspect I only need the /var/usm/ part there.

update-usm.sh does not exist in Porteus.

It exists in the Porteus forum. viewtopic.php?f=75&p=24697#p24697

[brokenman]

I recall requesting that you do not use this script with your setup. Updating should be done through the application itself which uses removepkg and installpkg (native slackware tools). If you don't heed my advice there is little I can do to help unless I can get a full directory listing (including hidden files) of your savefile.

Yes. To which USM says I am already current.

Do you mean it tells you that your current version (3.1.2) is the latest version? This is ODD since it takes the version line (USMVER=XXXXXX) from /etc/usm/usm.conf and cross checks it with the online version file. The 3.1.2 version usm.conf contains a different string than the current version.

It appears you may have some files stored in your save file and are missing others. Try forcing an update of usm by opening the file /etc/usm/usm.conf and changing the line that says:

USMVER=140804
to
USMVER=140803

Then run the update again. This should force a total update of the USM application by downloading the latest version, installing it over the top of the existing files leaving you with the current version 3.1.4 files.
To be clear, /var/usm only holds the database files for the various slackware repositories. The important files to update reside in /etc/usm/usm.conf and /usr/share/usm/*.

[Ed_P]

Thanks brokenman for trying to help but I've reverted to my 3.0 IPO. And today I was able to upgrade it from USM 3.1.12 to USM 3.1.14. However I couldn't update the USM databases becuase they all said they were already updated today. Somehow the 3.0.1 IPO must have updated the save.dat files? I don't know and I don't care at this point. Apparently release upgrades regardless of how minor require starting with a new empty save.dat file.

BTW I also didn't care for the 3.0.1's new Firefox tabs location.

ITo be clear, /var/usm only holds the database files for the various slackware repositories. The important files to update reside in /etc/usm/usm.conf and /usr/share/usm/*.

What about the /usr/bin/ files, usm* and packagetools?

[brokenman]

However I couldn't update the USM databases becuase they all said they were already updated today.

This feature was introduced in 3.1.4 to save time. If you manually update slacky, and then do usm -u all then it will skip slacky. It is controlled by updating the timestamp on the OPTIFEST files every time you update a database. If you need to force an update you can change the value on line 15 in /usr/share/usm/funcupdateDatabase from 86400 (24 hours) to however many seconds you want.

Somehow the 3.0.1 IPO must have updated the save.dat files?

Not sure I understand. The 3.0.1 release doesn't touch your save files. Only you affect them when you make a change, such as updating the USM database.

I don't know and I don't care at this point.

Fair enough.

Apparently release upgrades regardless of how minor require starting with a new empty save.dat file.

Certainly not.

The important files to update reside in /etc/usm/usm.conf and /usr/share/usm/*.

What about the /usr/bin/ files, usm* and packagetools?

At this stage no. They are rarely updated. All of the functions live in /usr/share/usm. In any case when you update in the recommended way, all the files are updated without exception.

[Ed_P]

Somehow the 3.0.1 IPO must have updated the save.dat files?

Not sure I understand. The 3.0.1 release doesn't touch your save files. Only you affect them when you make a change, such as updating the USM database.

Indirectly that's kinda of the problem. The 3.0.1 ISO has USM 3.1.14 but the save.dat has USM 3.1.12 and it was overriding the 3.0.1 ISO's version.

But with all the booting and rebooting and rebooting; GUI mode, A/F mode, with 3.0, with 3.01, restoring the live save.dat from a backup, etc. who knows what happened. But it seems that whenever I tried to update USM 3.1.12 to 3.1.14 yesterday USM GUI always told me I had the current version.

As I said

I don't know and I don't care at this point.

Apparently release upgrades regardless of how minor require starting with a new empty save.dat file.

Certainly not.

If they deal with USM it sure looks that way to me.

[brokenman]

Can anyone else confirm problems with updating USM after upgrading to 3.0.1?

[tome]

If usm.conf is modified by user (some settings), then it can be not updated because it resides in /mnt/live/memory/changes (updated usm.conf is in .../memory/images) - i think here is a bug.

Another bug found (i486):
Try:
usm -g enlight
....
/usr/share/usm/funcpackageGet: line 414:

[fanthom]

@tome
i think USM does upgrades by installing a txz package.
this would override files from changes.

[brokenman]

Correct. USM is updated by installing a slackware package which overwrites current config file.

The bug: /usr/share/usm/funcpackageGet: line 414 is reproducible here and when fixed uncovers another error. Thanks.

[Ed_P]

This is how you remove hte database files into a module:

Code: Select all

mkdir /tmp/db
cp -a --parents /var/usm/* /tmp/db
rm -rf /tmp/db/var/usm/local
dir2xzm /tmp/db /tmp/database-usm-20140513.xzm

OK I have a question concerning this approach. I put the db files into a module and I reboot with the usm database module in the modules folder so when I look at my var/usm folder they are there just like normal. But when I later reboot and my save.dat file is created won't it also backup the database files since they are a part of my save.dat folder grouping; etc, home, opt, root, usr and var?