Bounty $$: Termux ReactNative Integration issue support

[simbadMarino]

Hello termux community! I hope this is the right place to ask for your help. I'm running some issues while trying to integrate the termux app into a React Native app.

Looks like the installation of packages is done OK however I'm getting this error when lauching TermuxActivity:
exec("/data/data/com.justshare/files/usr/bin/login"): No such file or directory

with the following output in the Run window:

I/com.justshare: Background concurrent copying GC freed 5842(2286KB) AllocSpace objects, 0(0B) LOS objects, 17% free, 27MB/33MB, paused 960us total 540.557ms
I/com.justshare: Background young concurrent copying GC freed 89594(5243KB) AllocSpace objects, 0(0B) LOS objects, 15% free, 28MB/33MB, paused 8.651ms total 268.872ms
W/com.justshare: type=1400 audit(0.0:145): avc: granted { execute } for name="login" dev="vdc" ino=82904 scontext=u:r:untrusted_app_27:s0:c140,c256,c512,c768 tcontext=u:object_r:app_data_file:s0:c140,c256,c512,c768 tclass=file app=com.justshare
W/com.justshare: Accessing hidden field Ljava/io/FileDescriptor;->descriptor:I (greylist, reflection, allowed)

I'm attaching a brief gif showing the problem:

I have tried lots of different alternatives but I'm getting out of ideas honestly as I'm not a mobile dev expert neither totally understand termux code (even after weeks of study lol)

I'm offering a $40 US dollar bounty in crypto ( Monero, Ripple, TRX, BTT or any TRON token) to whoever finds a solution and publish it here first.

I think it should be a really easy to solve issue for you but honestly cannot see the light now and I'm a bit desperate to find a solution now lol.

Link to the complete repo: https://github.com/simbadMarino/dCloud

Let me know if you need additional info. Thanks and I hope I can your support :)

[agnostic-apollo]

You are directly using bootstrap.zip from termux-packages releases. Termux binaries are hardcoded to use and must be installed under the /data/data/com.termux/file/usr/ $PREFIX path. You cannot directly use termux compiled binaries in your app. You need to compile them specially for your app with the /data/data/com.justshare/files/usr prefix. Check following for how to build packages for yourself.

https://github.com/termux/termux-packages/wiki/Building-packages

https://github.com/termux/termux-packages/wiki/Termux-file-system-layout

You are currently also targeting sdk 28 so termux will work for now, but if you plan to publish on playstore or target sdk 29 plus then you will face other issues as well which you fine info for at the following link. In that case using android-10 branch app will be wiser.

https://github.com/termux/termux-packages/wiki/Termux-and-Android-10

[simbadMarino]

Hello @agnostic-apollo , thanks for your support! I've been learning and trying and following the wikis. I'm using your docker termux build environment and managed to create some .deb packages with a customized $PREFIX by running the build-package.sh script. Then I learned that I needed to run the generate-bootstraps.sh script in order to generate the zip file containing the minimal working environment. I edited properties.sh to change the $PREFIX to com.justshare and ran the script, however the script is only generating: etc, tmp and var folders. I was expecting a complete environment like the one available in the termux-app repository (bin, etc, include, lib, libexec, share, tmp, var, SYMLINKs.txt) and the same containing the login script which is the one currently failing to be executed in my app.

As a side note I didn't fully understand the following sentence about having an apt repository in the web server:

I used the https://dl.bintray.com/termux/termux-packages-24 repository as it looked to have more than enough packages for my purposes but not sure if running the script like: ./scripts/generate-bootstraps.sh --repository "https://dl.bintray.com/termux/termux-packages-24" should be enough as that's why I did to generate my bootstrap packages

Would you please advice on how to generate such a complete environment using my customized $PREFIX? I could not identify any section in the wiki talking about that.
Thanks a lot in advance!!

@simbadMarino

1. Compile packages with your custom prefix.
2. Create apt repository and push it to either local or remote web server. (you can use aptly to generate apt repository from given deb files)
3. Run generate-bootstraps.sh script with custom configuration (prefix & url).

It is not possible to use generate-bootstraps.sh without apt repository because it needs some metadata. It is not possible to use official packages to generate bootstrap archives with custom prefix. All three steps shown above are important.

[simbadMarino]

Thanks a lot! I will try those steps now I understood :) Sent from myMail for iOS Saturday, 3 April 2021 10:52 -0600 from ***@***.*** ***@***.***>: ***@***.***Marino

…

* Compile packages with your custom prefix. * Create apt repository and push it to either local or remote web server. * Run generate-bootstraps.sh script with custom configuration (prefix & url). It is not possible to use generate-bootstraps.sh without apt repository because it needs some metadata. It is not possible to use official packages to generate bootstrap archives with custom prefix. All three steps shown above are important. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or unsubscribe .

[agnostic-apollo]

@simbadMarino

Or you can try the following experimental build-bootstraps.sh script to locally cross-compile only the bootstrap package debs and create bootstrap zips. I wrote this a while ago and some stuff has changed in termux build systems by now. However, I have updated the script to work with current system so that you can use it, and it is working for a different PREFIX. There could of course be issues but likely solvable, I only ever did basic testing, didn't get time for more, although openssh works. On-device (termux in mobile) builds are not supported currently, so use PC (cross-compile in docker).

Firstly, you need to pull the latest changes from termux-packages repo, I just committed some stuff. (package source urls got outdated since old versions were removed by respective hosters)

Then

1. Set the TERMUX_APP_PACKAGE value in properties.sh to your app's package name.
   2. Place the build-bootstraps.sh in termux-packages/scripts directory.
2. Run cd termux-packages
3. Run ./scripts/run-docker.sh ./scripts/build-bootstraps.sh &> build.log to compile for all archs. You should find the bootstrap-*.zip in the termux-packages directory. If you want to compile only for a specific arch like aarch64, then run ./scripts/run-docker.sh ./scripts/build-bootstraps.sh --architectures aarch64 &> build.log. You can pass additional comma-separated list of packages that should be included in the bootstrap in addition to the default ones with the -add option.
4. Replace/place the zips in termux-app/app/src/main/cpp.
5. Add a return statement at start of downloadBootstrap() function in termux-app/app/build.gradle so that the custom bootstrap-*.zip files don't get replaced with termux ones.
6. Then build an APK. Untested, but should hopefully work.

It would be better if you ran ./clean.sh before building for a different prefix to start fresh, or pass -f option to build-bootstraps.sh script at least once (for each arch).

If you get curl: (18) transfer closed with x bytes remaining to read. while running build-bootstraps.sh when its downloading a package source, then just run the script again, it should hopefully work.

If you get curl: (22) The requested URL returned error: 410 Gone or something like 404 Not Found while running build-bootstraps.sh when its downloading a package source, then you will have to update the TERMUX_PKG_VERSION, TERMUX_PKG_SRCURL, etc in the build.sh file for the respective package, and fix any *.patch files or apply additional ones if compilation fails, or open an issue in termux-packages.

Good-luck!

build-bootstraps.zip

Edit:

build-bootstrap.sh is officially available in termux-packages repo, check https://github.com/termux/termux-packages/wiki/For-maintainers#build-bootstrap-archives.

[simbadMarino]

@agnostic-apollo I gotta say THANK YOU!!! The bootstrap package was successfully created and then I managed to make it work in my app. @agnostic-apollo , @xeffyr
Kindly share your Crypto address so I can transfer you what I promised (preferible !

I ran into another issue (Hopefully this is the last time I bother you) I got the following error when trying to install a package using dpkg (I built this package using the build-package.sh script and custom $PREFIX):

I even analyzed the dpkg binary in my bootstrap and could not find any hard-coded com.termux directory. I tried modifying different paths in the manifest and some other java classes but still could not find the root cause of the issue.
Do you know what could be causing that?

P.S. If you prefer I could become a Backer instead of the crypto bounty for some time to support the further development of termux, let me know what do you prefer :)

THANKS AGAIN!!

I got the following error when trying to install a package using dpkg

Few possible causes:

• You have built with the default Termux prefix.
• That's all due to lib-dpkg-path-remove.c.patch which still has hardcoded com.termux.
• Something went wrong when building bootstraps (e.g. script picked official deb files).

Run grep -r 'com.termux' $PREFIX to see affected binaries.

[agnostic-apollo]

@xeffyr I don't think the hard coded com.termux is part of the patch in lib-dpkg-path-remove.c.patch, right?

Anyways, @simbadMarino you likely compiled the package with the wrong package name. In my default bootstrap, with additional openssh and sshpass, I compiled with build-package.sh -a aarch64 git and installed git and pcre2 (dependency of git) with dpkg -i pcre2_10.36_aarch64.deb git_2.31.1_aarch64.deb and it installed just fine, even git init works. Moreover, I couldn't fine any hard coded com.termux strings in dpkg and git deb files. So try compiling again I guess.

And you are very welcome! :) I am glad to hear at least the bootstrap worked to start Termux app fork.

About the bounty, the help is usually free on my part so its not an obligation to give it. But if you still wanna give it, you can check out my donation links here. Currently, I haven't set any cryto though, not sure how I will get it in my bank even, so if one of the payment channels in the link work for you, then great, otherwise no issue. As for being a backer for termux, prioritize backing @xeffyr or @Grimler91 since they do a lot more maintenance than me and have done it for far longer.

Thanks

I don't think the hard coded com.termux is part of the patch

Ah, just looked over patches with grep, so assumed that was the case.

Then issue perhaps remains that one or more packages are still compiled with wrong prefix, either dpkg or git package which was attempted for installation with dpkg. All debs have files archived with absolute path (or relative to the Android rootfs).

[agnostic-apollo]

No worries, I was using a text editor.

Yeah, likely, a clean build should hopefully solve the issue.

[simbadMarino]

Hello @xeffyr I sent the XMR rewards this morning ;) (I had to leave my wallet sync for hours lol) and already sent an email to discuss details to you @agnostic-apollo

In regards of the issue, I removed all my current .deb files in the /deb folder and ran the bootstrap build script again, will check the results today afternoon and will come back with the results.

Thanks!

I sent the XMR rewards this morning

I see, thanks.

[agnostic-apollo]

In regards of the issue, I removed all my current .deb files in the /deb folder and ran the bootstrap build script again, will check the results today afternoon and will come back with the results.

Clearing debs is not enough. Already compiled source files will just be repacked as debs again. You need to run clean.sh before building or pass -f to build script so that already built files are cleared first. My build-bootstrap.sh script also supports the -f option, forgot to add text to its --help output.

[simbadMarino]

yep, I also cleaned everything with clean.sh and just being paranoiac added the -f option ;) . Let's see if it created the file succesfully later today :) (fingers crossed)