fdroidserver VS proot

According to the latest comment on this F-Droid bug report it looks like the problem should be finally fixed in the next F-Droid build server update.

Proprietary: - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11359 - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11361 - https://gitlab.com/fdroid/fdroiddata/-/commit/37e72d45f841b72b334f23f3e15a2e31fa8c4d56 - https://gitlab.com/fdroid/fdroidserver/-/issues/1004

Different solutions may be better for the different file types than a single download centre for everything. For example, for APKs, there's f-droid. You could selfhost fdroidserver and add your own repo to the f-droid client. This way, the APKs are distributed via an app store that's searchable and can be configured to auto update.

They were all on different days. I do test the app on my phone before releasing, and usually only release after not noticing anything for a few days of using the dev version. The reason for the time is a bug in the F-Droid server software that is used to generate the repo. The releases of GitHub have the correct date.

Note that F-Droid uses algorithm at https://gitlab.com/fdroid/fdroidserver/-/blob/2.1a0/fdroidserver/build.py#L746 to automatically detect built APKs, so ensure any modifications to location or file name are compliant. Auto updates are detected by checkupdates bot at https://gitlab.com/fdroid/fdroidserver/-/blob/master/fdroidserver/checkupdates.py

For the source of fdroidserver which creates the F-Droid repository in the end see here: https://gitlab.com/fdroid/fdroidserver

Clone the fork onto your local machine. You'd need to use linux or mac (windows doesn't work). Install https://gitlab.com/fdroid/fdroidserver.

yep, sadly F-droid doesn't have enough people working on it to keep on top of google's "new" app signatures yet. There was some progress, but then I gave up waiting and added their own repo until it's fixed.

I suspect some component was upgraded (glib?) and it use some functions that are not handled well by proot. Report issue to https://github.com/termux/proot/issues in order to have chances get it solved for yourself and others with this "black screen" problem.

I needed to look at your comment for 10 minutes before I got what you mean. So you want containers that run on any POSIX operating systems?

You can do this with ptrace() which is in POSIX, but its going to be slow for i/o heavy applications. Unfortunately POSIX doesn't provide anything else (seccomp would already be a step up). See also proot[1], gVisor[2] and User Mode Linux[3] which all use ptrace().

[1] https://github.com/termux/proot

[2] https://gvisor.dev/docs/architecture_guide/platforms/#implem...

[3] https://www.kernel.org/doc/html/v5.9/virt/uml/user_mode_linu...

Documentation does not exist. Just like in best traditions of open source software typically maintained by one person. Look the proot source code instead. Here is the link to extension source code: https://github.com/termux/proot/blob/master/src/extension/link2symlink/link2symlink.c

You'll probably want to do that inside of a proot environment.

Now regarding proot: it can't have higher privileges than your Termux shell session, despite the user "root" which may possibly appear. It was told many times here on Reddit, Termux GitHub and even Wiki (https://wiki.termux.com/wiki/PRoot) that PRoot does not give extra privileges and root user is fake.

I understand the sentiment, but I disagree. From the last time I checked, the big compromise with GNU/Linux phones is still the lack of social media and messaging apps and appstore ecosystem. Android, with root, is every bit as much a computer as a Pinephone and Librem 5, but the opposite isn't true. Termux has PRoot, a user-space implementation of chroot allowing a full distro install. I personally don't have any problem depending on Google, I have a problem with things being locked away with no alternative. Given the option, I will happily accept the risks and void my warray to root.

https://wiki.termux.com/wiki/PRoot