Strange bug in USM 3.2.0

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.
Shadow0815
Black ninja
Black ninja
Posts: 33
Joined: 16 Jul 2015, 03:50
Distribution: Porteus,Xubuntu,Arch
Location: DE

Strange bug in USM 3.2.0

Post#1 by Shadow0815 » 26 Apr 2019, 12:45

using Porteus 4.0 xfce x86_64 USM version: 3.2.0

if i do:
usm -g nano-2.6.0-x86_64-1.txz

it works.

but the moment i create directory p USM stops working:

#---------------
root@vm:~# mkdir p
root@vm:~# usm -g nano-2.6.0-x86_64-1.txz
#---------------

Getting error:

/usr/share/usm/funcpackageGet: line 103: declare: 456K: value too great for base (error token is "456K")

(changing directory without subdirectory p USM starts working again)


That also means if i have certain files
like symlink p to my porteus usb stick in my homedir
THE GUI USM fails without any error messages.

I know other file/symlink/directory names than p also cause this problem but i don't know the pattern behind this.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Strange bug in USM 3.2.0

Post#2 by Ed_P » 26 Apr 2019, 20:18

:%) What happens if you create the module without the p symlink? What happens if you mkdir y instead?

If your USB stick is mounted I don't see the need for the symlink. :unknown:
Ed

Post Reply