Page 16 of 25

Re: USM Unified Slackware Package Manager

Posted: 02 Aug 2014, 17:50
by router
i am, and a 5 minutely cron dump-session. shall i try without that cheatcode?

i'm new to porteus, very new, but i'd appreciate any info about these things that can be given so i learn not just what to do or not but the reasons. :)

edited to add, i've now seen the discussion in the USM bugs thread, the info about whiteout files is beyond my current grasp of how Porteus works but i gather enough from context that the net result is a save-state with inconsistencies. let me be silent here and i'll post there if i have something of relevance, or questions, as i think this should be clean and more for "new version is ready, get it here" kind of things.

Re: USM Unified Slackware Package Manager

Posted: 02 Aug 2014, 18:18
by Ed_P
router wrote:i'm new to porteus, very new, but i'd appreciate any info about these things
We were all new at one point, myself included, and I still am.

Copy and paste this script into your /home/guest folder.

Code: Select all

#!/bin/sh 
# http://forum.porteus.org/viewtopic.php?f=81&t=3501&p=25182#p25178
# http://forum.porteus.org/viewtopic.php?f=81&t=3501&p=25151#p25162
# http://forum.porteus.org/viewtopic.php?f=81&t=3501&p=25151#p25178

# mloop requires changes= cheatcodes not be used (Always Fresh mode)

if [ `whoami` != "root" ]; then
   ktsuss "$0"
   exit
fi

if [ -f /mnt/live/memory/images/changes ]; then
   SPACEDATDIR=/mnt/live/memory/images/changes 
else
   mloop /mnt/sda5/porteus/changes/porteussave.dat
   SPACEDATDIR=/mnt/loop
fi

echo find ${SPACEDATDIR} -name .wh.*
find ${SPACEDATDIR} -name .wh.*
echo
echo Enter to delete, Ctrl+C to exit.
read
echo "find ${SPACEDATDIR} -name .wh.* | xargs rm"
find ${SPACEDATDIR} -name ".wh.*" | xargs rm
echo
echo find ${SPACEDATDIR} -name .wh.*
find ${SPACEDATDIR} -name .wh.*

read
if [ -f /mnt/live/memory/images/changes ]; then
   exit
else
   uloop 
fi
exit
Change the "mloop /mnt/sda5/porteus/changes/porteussave.dat" line to match your path and file name.

I save the file as savedatremovewhfiles.sh and run it with:

Code: Select all

sh savedatremovewhfiles.sh
If you choose a difference file name to save it to then change the sh command to match your name. Then reboot and USM should work. If not save the script to a place outside of Porteus, boot to Always Fresh mode and rerun the script.

This is a known bug and will be fixed in the not too distant future.

http://forum.porteus.org/viewtopic.php? ... =90#p26629

Re: USM Unified Slackware Package Manager

Posted: 02 Aug 2014, 19:46
by brokenman
Router, no need to use any scripts or delete any file (please). Don't mess around with the .wh files at all. Just download the new initrd.xz and replace the one in your current porteus install. It is located in: /mnt/sdxY/boot/syslinux/initrd.xz (where sdxY is the location of your porteus install.)

The error message will still appear but won't affect the functioning of Porteus in any way. It is a USM error that will be fixed in the next update.

EDIT: You may need to start your savefile.dat again from scratch but it beats getting into to trouble with .wh files in the future and compounding the problem. Kill it at the root and use the new initrd.xz.

Re: USM Unified Slackware Package Manager

Posted: 02 Aug 2014, 22:53
by Ed_P
brokenman wrote:Router, no need to use any scripts or delete any file
Instead just...
start your savefile.dat again from scratch
delete everything. :lol:

But it is an option and I've been there and done that, many times. Thus I have a script for that too. What I do is create a backup of my current save.dat file, then create a new save.dat file, reboot and use this script to copy my pertinent files from my backup to my new system.

Code: Select all

#!/bin/sh

# 1. Create a new save.dat file. menu > System Tools > Porteus save file manager
# 2. Exit Porteus and reboot to Windows or Porteus Always Fresh mode
# 3. Backup save.dat to save.dat.zxm
# 4. Rename save.dat to save-1.dat
# 5. Rename save-2.dat to save.dat
# 6. Reboot Porteus.  It will appear as an Always Fresh mode boot.
# 7. Run this script. sh /mnt/sda5/porteus/Guest/RebuildSavedat.sh

if [ `whoami` != "root" ]; then
  ktsuss "$0"
  exit
fi

echo
echo Before starting:
echo
echo Be sure to verify the SAVEDATBKUP file\'s name and location.
echo
echo "Set the Time Zone to US/Eastern to correct Date & Time for saved files."
echo "Menu > System Tools > Porteus Settings Centre > System Settings > Time Config"
echo
echo Run this script from LXterminal else SpaceFM bookmarks will not be restored.
echo Run the wmWeather.sh script and Firefox to initialize their folders.
echo And set width of the this window to be 130+.
echo
read

SAVEDATBKUP=/mnt/sda5/porteus/modsavedat/porteussave.dat.xzm

mloop  $SAVEDATBKUP
cp -r -d    /mnt/loop/home/guest/*                     /home/guest/
cp -r -d    /mnt/loop/home/guest/.asoundrc             /home/guest/

cp -r -d -v /mnt/loop/home/guest/.config/lxterminal/*           /home/guest/.config/lxterminal/ 
cp -r -d -v /mnt/loop/home/guest/.config/keepassx/*             /home/guest/.config/keepassx/
cp -r -d -v /mnt/loop/home/guest/.config/spaceFM/bookmarks      /home/guest/.config/spacefm/
cp -r -d -v /mnt/loop/home/guest/.config/wmWeather/*            /home/guest/.wmweather/

# disables the Acer's touchpad's jumping
# http://forum.porteus.org/viewtopic.php?f=81&t=1955&start=45#p13596
cp -a       /home/guest/syndaemon.desktop              /home/guest/.config/autostart

# No sound - on an Acer 722 netbook
# http://forum.porteus.org/viewtopic.php?f=81&t=2926#p20365
cp -a       /home/guest/asound.conf                    /etc/
/etc/rc.d/rc.alsa restart

cp -r -d -v /mnt/loop/etc/NetworkManager/system-connections/* /etc/NetworkManager/system-connections/ 
echo 

# http://forum.porteus.org/viewtopic.php?f=117&t=3551&p=25812#p25812
cp -r -d -v /mnt/loop/etc/localtime                           /etc/

# http://forum.porteus.org/viewtopic.php?f=123&t=3265&p=26041#p26008
cp -r -d -v /mnt/loop/etc/profile.d/add-z-dot*                /etc/profile.d/

echo 
echo Be sure Firefox is closed, then press Enter to continue.
read

cp -r -d -v /mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/places.sqlite /home/guest/.mozilla/firefox/c3pp43bg.default/
cp -r -d -v /mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js      /home/guest/.mozilla/firefox/c3pp43bg.default/
cp -r -d -v /mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/signons.sql*  /home/guest/.mozilla/firefox/c3pp43bg.default/
echo
ls /home/guest/.mozilla/firefox/c3pp43bg.default/
echo
echo Press Enter to restore USM files.
read

cp -r -d -v /mnt/loop/usr/bin/usm*                                /usr/bin/
cp -r -d -v /mnt/loop/usr/bin/packagetools                        /usr/bin/
cp -r -d -v /mnt/loop/usr/share/applications/usm.desktop          /usr/share/applications/
cp -r -d -v /mnt/loop/usr/share/icons/hicolor/48x48/apps/usm*.png /usr/share/icons/hicolor/48x48/apps/ 
cp -r -d -v /mnt/loop/etc/usm/*                                   /etc/usm/
cp -r -d -v /mnt/loop/usr/share/usm/*                             /usr/share/usm/
cp -r -d -v /mnt/loop/usr/man/man8/usm.8*                         /usr/man/man8/
cp -r -d    /mnt/loop/var/usm/*                                   /var/usm/
ls /var/usm/ 
echo
echo Press Enter to continue.
read

uloop

echo
echo "Use Preferences > Razor-qt settings > Razor Autosuspend to set Lid Closed to Sleep"
echo "   and Power Low to Shutdown."
echo "Use Accessories > HP Device Manager > Setup Device to activate Network HP printer." 
echo "Use Porteus > Preferences > Java to change Security settings for Java games."
echo
echo Open FireFox to verify History Preferences. 
echo "  Edit>Preferences>Privacy>History>Use custom settings for history:"
echo "   Accept cookies, Accept third-party cookies, Keep until: I close FF, Clear history"
echo "   and change browser.bookmarks.max_backups setting to 4 {about:config}."
echo
echo Recreate the porteussave.dat.xzm file.
echo 

exit
You will need to modify the SAVEDATBKUP setting to fit your environment. And delete the app restores that you don't use like wmWeather and keepassx.

And if it doesn't work you can always
brokenman wrote:start your savefile.dat again from scratch

Re: USM Unified Slackware Package Manager

Posted: 02 Aug 2014, 23:07
by brokenman
But it is an option and I've been there and done that, many times.
Yeah you're probably right. Listen to the pro router.

For the record of not being quoted out of context. I believe I said ... " You may need to start your savefile.dat again from scratch". I assume since you've just installed Porteus that it is not a big deal.

Re: USM Unified Slackware Package Manager

Posted: 03 Aug 2014, 04:54
by router
well i'm using kde anyway not lxde

and yes at this point i'm just playing with things, i dont have that much of importance to be bothered much about clean start, and i've anyway managed to hose my install with something i did unrelated to usm, in attempting to make a module of an application work

this application has in its own file structure the folders /etc and /lib and since i made the module a bit wrong, it overlaid the 'real' /etc and /lib with its own :wall: :lol:

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?

Re: USM Unified Slackware Package Manager

Posted: 05 Aug 2014, 03:00
by brokenman
+-------------------------
Thu Jul 31 18:05:13 UTC 2014
Added some checks to sbo build
Fixed warning message on update
Added skip update if updated less than 24 hours ago
Added support for authenticated proxy (Thanks Blaze)

+-------------------------
Tue Jul 29 21:12:32 UTC 2014
Fixed merge modules name (thanks Ed_P)
Sent edit config GUI to background (thanks Bogomips)
Fixed system libs report malfunction (thanks Bogomips)
Added GUI option for no prompts
Fixed set path option (thanks Tome)
Remove old updates before install (thanks roadie)

Updated to 3.1.4 which will be included in next Porteus release. Fixes harmless warning when updating. Adds support for authenticated proxy. Also pushed database update.

Re: USM Unified Slackware Package Manager

Posted: 05 Aug 2014, 05:29
by Ed_P
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.

Re: USM Unified Slackware Package Manager

Posted: 05 Aug 2014, 14:03
by brokenman
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)

Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 02:24
by brokenman
+-------------------------
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

Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 05:53
by Ed_P
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




Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 06:28
by fanthom
@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

Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 12:29
by Bogomips

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 

Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 13:10
by fanthom

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.

Re: USM Unified Slackware Package Manager

Posted: 22 Aug 2014, 14:24
by brokenman
@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.