TermuxArch / TermuxArch

Experience the pleasure of the Linux command prompt in Android, Chromebook, Fire OS and Windows on smartphone, smartTV, tablet and wearable https://termuxarch.github.io/TermuxArch/

Home Page:https://termuxarch.github.io/TermuxArch/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

TermuxArch WARNING: Generated script signal 127 near or at line number 623 by '_ADDMOTD_'! Please run 'bash setupTermuxArch.bash' again or use 'bash setupTermuxArch.bash refresh'.

JanuszChmiel opened this issue · comments

I have found one bug inside scripts when running Setuptermuxarch.bash script. It is new error and it has never appeared before.

Here are The outputs

Signal generated in 'proot PREPROOT necessaryfunctions.bash'; Cannot complete task; Continuing...

If you find improvements for 'setupTermuxArch.bash' please open an issue and an accompanying pull request. A pull request can assist in shedding more light on an issue.

đź•› > đź•™ Cleaning up installation files: DONE

🕛 > 🕤 Arch Linux in Termux PRoot is installed. Configuring and updating Arch Linux 📲 necessaryfunctions.bash: line 623: ADDMOTD: command not found

TermuxArch WARNING: Generated script signal 127 near or at line number 623 by 'ADDMOTD'!
Please run 'bash setupTermuxArch.bash' again or use 'bash setupTermuxArch.bash refresh'.

The command 'bash setupTermuxArch.bash help' has information how to use 'setupTermuxArch.bash'.
The command 'bash setupTermuxArch.bash help' has information how to use 'setupTermuxArch.bash'.

setupTermuxArch.bash version 2.0.1443: [Exit Signal 201] DONE �

~ $
~ $

I AM using The latest up to date stable Termux version 118. And I run apt update and apt upgrade regularly to make my best so Termux is up to date.

Here are The outputs

Thank you for opening this issue @JanuszChmiel and sharing output, and the fact that the system on the device is up to date. There were major changes to almost all of the base scripts in TermuxArch for code legibility and end user performance reasons aimed at more features and ease of use for both the BASH coder and the end user in the last few weeks.

As more users may encounter this error, it should be mitigated. Can you please try rerunning the command after the update to see whether it works as expected? It should work as expected.

I have rerun bash setupTermuxArch.bash a number of times, and it performed as expected. It updated itself as should be at this moment in time on the first run and began installing Arch Linux in Termux PRoot each and every time successfully. I do not see any errors at present.

The errors I did find during earlier writing and debugging were dissimilar to the one you found and reported. Thank you!

Is the command that you wanted run successfully on the first try; bash setupTermuxArch.bash?

a) What is the full command you are using?
b) Can you please try rerunning the command after the update to see whether it works as expected?

Setting locales to: Language >> en_US << Region: Please wait a moment.
archlinuxconfig.bash: line 1850: CPUABIX8664: unbound variable
setupTermuxArch  2.0.1046: [Exit Signal 1] DONE 🏁

There was an interesting unbound [Exit Signal 1] update from a much older VERSIONID=2.0.1280 generated on armv7l with updated packages which are benign and seem to continually show once again that BASH code behaves as expected year after year. I will try to make it clearer to attempt rerunning the last command if the updated version of setupTermuxArch.bash interpretted the command unsuccessfully and exited:

[[ -z "${ARGS:-}" ]] && printf "\\n\\e[1;32mFile \\e[0;32m'%s'\\e[1;32m was UPDATED\\e[1;34m:\\e[0;32m Please run 'bash %s' again if this automatic update was unsuccessful.\\n\\n\\e[1;32mRESTARTED \\e[0;32m'%s'\\e[1;34m:\\e[1;32m CONTINUING...\\n\\n\\e[0m" "${0##*/}" "${0##*/}" "${0##*/}" || printf "\\n\\e[1;32mFile \\e[0;32m'%s'\\e[1;32m was UPDATED\\e[1;34m:\\e[0;32m run 'bash %s' again if this automatic update was unsuccessful; You should be able to use the '!!' command to run '%s' again.\\n\\e[1;32mRESTARTED \\e[0;32m'%s'\\e[1;34m:\\e[1;32m CONTINUING...\\n\\n\\e[0m" "${0##*/}" "${0##*/} $ARGS" "${0##*/} $ARGS" "${0##*/} $ARGS"

a) amend readme
b) amend exit code

@JanuszChmiel I just noticed Please run 'bash setupTermuxArch.bash' again or use 'bash setupTermuxArch.bash refresh' in the output that you kindly shared, so simply running either commands should resolve this exit error on your machine. Please let me know if this was unsuccessfull.

🕛 > 🕗 Not removing files after checking download integrity with md5sum. 🕛 > 🕤 Arch Linux in Termux PRoot is installed. Configuring and updating Arch Linux 📲 necessaryfunctions.bash: line 652: _ADDMOTD_: command not found
Screenshot_20220129-044347

This result looks much more promising; Hopefully I will find the time to resolve 652: _ADDMOTD_ today.

_ADDMOTD_ WARNING resolved with this da05703 git commit. Thank you so much for sharing this issue quickly @JanuszChmiel 🎼 🎵 🎶 🎐

You might also be interested in the new finding external cache storage feature that is being implemented into USECACHEDIR in setupTermuxArchConfigs.bash. It might be accessible via USECACHEDIR=1 ## change to 0 to use cache dir in this file in the near future.

This feature is intended for end users and developers to use in order to recreate the Arch Linux in Termux PRoot system easily and quickly on device from cache. It should be used in conjunction with KEEP=0 during the initial installation of the Arch Linux system from the Internet.

Automated external micro sdcard storage cache is a goal still to be achieved. Hopefully, it will be soon.

PRs requested at https://github.com/shlibs/shlibs.bash/pulls and https://github.com/shlibs/shlibs.sh/pulls and https://github.com/TermuxArch/TermuxArch/pulls and more! Please.

If you have time, and more importantly space on device to use TermuxArch cache, then please share your thoughts about this feature intended for system installation and restoration.

localisation to Czech language fail

Is this condition still true after the fix?

localisation to Czech language fail

If you are still having localization issues, please open a new issue here. Also, feel free to submit a new PR here. A clearly submitted pull request is preffered over an issue in most cases. Both are eagerly accepted at this project.