sudoers file is apparently absent in the latest TermuxArch v2.0.519 about termuxarch HOT 12 CLOSED

This commit 10db9b3 add support support for sudoers file absence.

from termuxarch.

[root14:07~]$ addauser a
Adding Arch Linux in Termux PRoot user 'a' and creating Arch Linux in Termux PRoot user a's home directory in /home/a...
passwd: password expiry information changed. Added Arch Linux in Termux PRoot user 'a' and configured user 'a' for use with the Arch Linux command 'sudo'. Created Arch Linux user a's home directory in /home/a. To use this account run 'startarch login a' from the shell in Termux. To add user accounts you can use 'addauser a' in Arch Linux and 'startarch c[ommand] addauser a' in the default Termux shell. Please remember not to nest proot in proot unknowingly by using 'startarch' in 'startarch' as this is known to cause issues for PRoot users.
addauser 2.0.519: DONE 🏁

This might sound surprising to you @xd003, I encountered a similar message hours ago. You could say the exact same anomaly as the one above with one of the updates that I was using a couple of hours ago today too.

As far as I can tell, this is now resolved with the same version 2.0.519 number and commit. I have no idea how a program that has checksums can morph. Delayed app updates cannot really be an issue, or can they?

Checksum checks usually flare. I have noticed that sometimes check sums briefly fail due to the update process. This happens fairly rarely.

This issue looks like an anomaly category issue to me; Do do you agree?

from termuxarch.

Try refresh. If not then please try reinstall and see if the error persists. Refreshing the system should suffice.

I just checked between the last message and now: two successful outcomes as root user with the same version number and one more successful with sudo v2.0.518 in a user account.

from termuxarch.

This message that showed on our screens at approximately the same time has been gone for hours. Two new fresh v2.0.519 installations are attempting into makeyay...

Do you have any insight into this issue @xd003, as I cannot explain it?

from termuxarch.

Try refresh. If not then please try reinstall and see if the error persists. Refreshing the system should suffice.

I just checked between the last message and now: two successful outcomes as root user with the same version number and one more successful with sudo v2.0.518 in a user account.

Yes you are correct
I just ran ./setupTermuxArch refresh and it has resolved that issue .Now sudoers file is present, pretty weird why it had happened earlier . To properly get the hold of such anomalies , i think if TermuxArch saves the debug output of the bash installation in a separate file ( probably in /var/backups/arch), it could help to analyse if something abnormally went wrong later

from termuxarch.

This commit 1f0ee1e might have anomalies as well. The jump in the version number is explainable because there have been updates to the repository, but not the script. When I search this commit web page for CHANGE:

How would you explain that the checksum has changed, but the file CHANGE.log does not appear to have changed in about a month?

the debug output of the bash installation in a separate file ( probably in /var/backups/arch), it could help to analyse if something

This is a very interesting idea @xd003! Can you outline how you would go about implementing a setup.log file?

from termuxarch.

Two new fresh v2.0.519 installations are attempting into makeyay...

Both made yay correctly. On one device there was a little free space left, and yay heroku-cli built as expected.

from termuxarch.

@JanuszChmiel just opened issue setuptermuxarch script causes error #69. This commit 812435d kind of illustrates what we are dealing with here in this issue @xd003 as far as finding anomalies while using smartphones is concerned.

Please notice this modification only includes the brackets in STIME="$(SDATE) which should be STIME="$SDATE, and the relevant file changes. Have you noticed any similar anomalies in your computer work?

from termuxarch.

fortunately to be found and usually quickly corrected, sometimes not, @xd003 and I are discussing an error which magically appeared the night before, then apparently disappeared by itself at this #24 issue.

@JanuszChmiel thank you once more for sharing news about this error so quickly. I was thinking about this anomaly and the one mentioned in issue 24 and its impact on the user base.

To sum up, this error that you found @JanuszChmiel potentially impacted a lot of users, many users and could have remained undetected for quite some time. The reason being is that the effects of this error affects older model devices and/or older Android applications. And as far as we know the unsupported post Android 4 user base is enormous.

Reprint from SDRausty/termux-archlinux#69

In view of this new event, I am really really glad that you @xd003 had opened this issue. Thank you again 🎵 🎶

from termuxarch.

I do not really want to be wasting your time @xd003, and even though this SDRausty/termux-archlinux@3e05493 commit is not at this repository it does affect this project. Can you compare commits 1f0ee1e 812435d and commit SDRausty/termux-archlinux@3e05493?

Technically these commits should be close to identical, even though they were crested on different machines, and pushed to different git reporitories at GitHub. Can you please summarize the differences between them when you have some spare time?

from termuxarch.

The reason I am bringing this up is I do not quite understand what is happening from this point on in the commit:
92c117b5330f2f0ef669c3dd31263dbd5c7fcb944b0d744e7d5e58b5f5ba555ce23f36682fd7c1afe4dbe3e32a4d1d46bb9ce86375bf042d9e17746e020fef02 ./setupTermuxArch
SDRausty/termux-archlinux@3e05493#diff-826f218ca0ba636cf35958f862d3fc96R3
494c1a4bbb505fb3009f0e434530b6401adf6fb502fd0f01eb31b757e6dd397fd2e78dc603ef03de0f86faaa25fcb763f1b5b8c2aa397ff8f5cbda6728351722 ./NOTICE.md SDRausty/termux-archlinux@3e05493#diff-826f218ca0ba636cf35958f862d3fc96R2

The question, it should be simple. Why are some checksums rewritten when there is no apparent change?

from termuxarch.

I had decided to do something that is not usually done as far as I know. I decided to dedicate two machines to installing new installs of Arch Linux in Termux PRoot in each one. The result is success, including building yay with command makeyay x3. On one of these smartphones I decided to install concurrent installations see how this feature works again.

Of the three successful installs @xd003, there were more than three attempts. An unsuccessful attempt ran into the same message that this issue is primarily about, and I took a very very close look at possible similar signals that preceded this one:

/etc/sudoers: No such file or directory

And there were some. It appears that somehow the data connection had prevented the sudo package install. No data connection can bring about this result. Do you think that this is possible in your case?

from termuxarch.