Page 1 of 1

Command "activate" within a script: Error

Posted: 29 Aug 2024, 08:52
by Kulle
the activate command within a script does not function correctly

1.) Module buici-clock in the modules directory
works

2.) Module buici-clock in the apps directory
Double-click on the module ==> Module works

3.) Module in the apps directory, and script run.sh also in this directory.
The command in the script
echo toor | sudo -S activate buici-clock_0.4.9.4+nmu2_amd64.xzm
does not work.

Error message: module is not valid module

I then have to close the window manually, and the module is then correctly activated and works.

How can I ensure that this error message does not appear,
and that I don't have to intervene manually?
Thank you very much

Command "activate" within a script: Error

Posted: 29 Aug 2024, 13:11
by reisub
Try putting quotes around the module's name or specifying the module's name with a ? where the + sign is.

Command "activate" within a script: Error

Posted: 29 Aug 2024, 14:25
by Kulle
Hi reisub,
I have tried your suggestions. no success.
then I renamed the module to clock.xzm.
Also no success.
The error has remained !
And now ?!

Command "activate" within a script: Error

Posted: 29 Aug 2024, 15:30
by beny
guest@porteus:/mnt/sdh1/porteus/optional$ echo toor | sudo -s activate kodi-21.0-7-x86_64.xzm
Password:
Updating shared library links: /sbin/ldconfig
guest@porteus:/mnt/sdh1/porteus/optional$

hi maybe the script have to run into the packages directory,if you add the guest user to sudo you don't need to write root password,but as usual i can go wrong on this ....

Command "activate" within a script: Error

Posted: 29 Aug 2024, 22:23
by reisub
Thoughts: Put the clock.xzm in the /modules directory, it should load automatically when you boot. Another option if you want the clock.xzm to be in a different directory use the boot parm extramod= cheatcode pointing to the other directory.

Command "activate" within a script: Error

Posted: 29 Aug 2024, 22:34
by beny
hi, the kodi package is located in optional directory,not modules,maybe the -s after sudo instead of -S