This is the version. And I haven't upgrade to the one he just posted.Ed_P wrote:What does usm -v show you? (you need to do su & toor 1st)
Code: Select all
guest@porteus:~$ su
Password:
root@porteus:/home/guest# usm -v
You are using USM version: 3.2.0
root@porteus:/home/guest#I think your right but I think it for those who didn't upgrade to 001, 002 and 003 when he release it.Bogomips wrote:Downloaded and tried. As far as I can tell no difference with rc4+.
The difference is that the usm-3.2 that shipped with rc4 is pulling from slackware-14.1. Meaning that the LIBS.TXT was generated from the slackware-14.1 repo. The new usm-3.2 that I uploaded is pulling from the slackware-14.2 repos. The LIBS.TXT file is generated from the slackware-14.2 repository. From a user's point of view you probably wouldn't notice any difference, but the difference is there.Downloaded and tried. As far as I can tell no difference with rc4+
I receive the same error.lordVortex wrote:Upgraded USM and databases (no databases were present before). I successfully downloaded ISO Master, but trying to download PCManFM gave an error of a missing LIBS.TXT. I checked all folders in /var/usm, LIBS.TXT were in all except sbo (filename was lower case in local folder). Running Porteus 3.2rc4 MATE, with new 001, 002, and 003-mate xzms.
Screenshot:
Any idea what could've caused it? I wanna dig through the usm scripts to see if I can find it, but I doubt I will. I'm not that good at bash scripts.Jack wrote:I receive the same error.lordVortex wrote:Upgraded USM and databases (no databases were present before). I successfully downloaded ISO Master, but trying to download PCManFM gave an error of a missing LIBS.TXT. I checked all folders in /var/usm, LIBS.TXT were in all except sbo (filename was lower case in local folder). Running Porteus 3.2rc4 MATE, with new 001, 002, and 003-mate xzms.
Screenshot:
Code: Select all
## Find distro that has dependency
TARGLIB=`find -L $DBDIR -type f -name "LIBS.TXT" | xargs grep -i "^$PKG" | head -n1 | awk -F: '{print$1}'`
[ $CLI ] && [ -z $TARGLIB ] && fatality "$SCRIPT $FUNCNAME $LINENO" "`gettext "Please wait 6 hours for the next database update. Could not find:"`" "LIBS.TXT"
[ $GUI ] && [ -z $TARGLIB ] && { echo "`gettext "Please wait 6 hours for the next database update. Could not find:"`" "LIBS.TXT" > $TMPDIR/.stream; gtk_message2 "`gettext "Fatal error"`" "LIBS.TXT"; exit; }
Code: Select all
root@porteus:/var/usm# find -type f -name "LIBS.TXT" | xargs grep -i "^libfm.so" | head -n1 | awk -F: '{print$1}'
root@porteus:/var/usm# find -type f -name "LIBS.TXT" | xargs grep -i "^libfm-1.2.4-x86_64-2ponce.txz" | head -n1 | awk -F: '{print$1}
>
> '
./ponce/LIBS.TXT
root@porteus:/var/usm# [ -z ./ponce/LIBS.TXT ]
root@porteus:/var/usm# [ -z ./ponce/LIBS.TXT ] && echo "Test"
root@porteus:/var/usm# find -type f -name "LIBS.TXT" | xargs grep -i "^libfm-extra-1.2.4-x86_64-1alien.txz" | head -n1 | awk -F: '{print$1}'
root@porteus:/var/usm# find -type f -name "LIBS.TXT" | xargs grep -i "^libfm-extra*" | head -n1 | awk -F: '{print$1}'
./slackonly/LIBS.TXT
root@porteus:/var/usm# find -type f -name "LIBS.TXT" | xargs grep -i "^libfm-1.2.4-x86_64-2ponce.txz" | head -n1 | awk -F: '{print$1}'
./ponce/LIBS.TXT
root@porteus:/var/usm#
Just noticed this.brokenman wrote:Please keep in mind that updating of the databases is done manually at the moment while still in testing
