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#
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#
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)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?
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
Code: Select all
nodeps: No dpepndency resolution.
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
Code: Select all
root@porteus:/home/guest# usm -v
You are missing required database files!
Please run: usm -u all
root@porteus:/home/guest#
Code: Select all
awk -F= '/USMVERSION/{print$NF}' /etc/usm/usm.conf
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
So to should the '-u usm' option.fanthom wrote:besides: '-v' flag should be documented in the usm help.
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?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.
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#
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
Code: Select all
/mnt/live/memory/changes/etc/usm/.wh.extra-deps.txt
root@porteus:/home/guest# ls /tmp/usm/
root@porteus:/home/guest#
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.Aug 5 04:43 /tmp/usm/usm-latest-0.0-noarch-1.txz
Will do.So to should the '-u usm' option.
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.I thought the new initrc file in 3.0.1 was a fix for that.
It doesn't at all. I was referring to the hang you are having when updating databases.And how does that impact the updating of usm itself?
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=EXITOr, from another point, how do I upgrade to 3.1.5?
And we are cross posting.brokenman wrote: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=EXITOr, from another point, how do I upgrade to 3.1.5?
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.
No. Please add EDIT: when updating previous posts so it is known that they were updated after the original post.Have you seen my updates?
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.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 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.The update-usm.sh approach seems to be frowned upon.
brokenman wrote:Any chance you have a .1 file in /tmp/usm? This bug was addressed in a previous versionAug 5 04:43 /tmp/usm/usm-latest-0.0-noarch-1.txz
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
Another possibility: old usm*.txz packages removed and old file downloaded?brokenman wrote:and all old usm*.txz packages are now removed before downloading of new packages.
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.confAnother possibility: old usm*.txz packages removed and old file downloaded.