On my samsung phone I can... for now.
Edit: oh, by android distributions I meant the varkous variants put on devices by manufacterers.
Custom roms probably wouldn't have these restrictions.
On my samsung phone I can... for now.
Edit: oh, by android distributions I meant the varkous variants put on devices by manufacterers.
Custom roms probably wouldn't have these restrictions.
https://www.reddit.com/r/termux/comments/1gks9mf/announcement_termux_broken_on_android_15_for/
https://www.reddit.com/r/oneplus/comments/1go55ow/termux_is_now_officially_dead_for_oneplus_and/
Termux is broken on oneplus devices.
This means winlator, and other similar termux based projects will no longer work.
In addition to that, other Android distributions have also moved "child process limit" to developer options, which may forebode them removing it, and breaking termux entirely. This is pretty scary IMO.
Personally, I am loving flux right now. I'm using it to set up my homelab right now, while I learn kubernetes.
I chose flux because it seemed lighter, without a web ui or any extra components I may not want. Using flux feels like getting the declarativity that nixos promised but couldn't really deliver on.
Also, I did note on another post, that Forgejo, who used to use imperative kubernetes for everything, is now switching to fluxcd.
Did you use flux 1, or flux 2?
Flux 2 is a complete rewrite, and is basically a different app.
Does forgejo really have an integrated CI/CD? I see this article, but it says it was put in beta, and no real notes after that. Although, it does look like the forgejo runner is a fork of https://github.com/nektos/act, which is a tool designed to be compatible with Github Actions, so that looks promising.
flux, Argo (better than flux)
Why Argo better than flux? The only real difference I know about is that argo has a web GUI built in, whereas flux does not.
Is there a specific android app you need?
https://gitlab.com/android_translation_layer/android_translation_layer/
And of course waydroid. Both these solutions let you run android app on Linux, but like wine, they won't work for every app.
Waydroid probably works for all apps not dependent on google though. But it's more difficult to set up than the android translation layer.
Debian already has docker packaged. That's more convenient.
Debian with the docker convenience script.
They seem to be moving away from this, and it's not longer the first option on their install page
On their debian page
Use a convenience script. Only recommended for testing and development environments
Also, it should be noted about the first option they recommend, Docker Desktop, that Docker Desktop is proprietary.
I recommend just getting the docker.io
and docker-compose
from debian's repositories.
Ubuntu in WSL comes with systemd enabled. Debian doesn't, and you have to enable it yourself.
That's why I chose to have people use Ubuntu in WSL, despite the other downsides. One less step to setup a Linux environment on Windows makes the process smoother.
Wish I could transcend into declarativity but the thread’s nix survivor ratio is grim
Yeah lol.
I will say, that for my server, I decided to use kubernetes + fluxcd for declaratively. My entire kubernetes "state" is declared in a git repo, and this is the popular, industry standard for things like this, called GitOps. It makes it very easy to add an app, since it's just adding a folder + some new config files. And unlike Nix, Kubernetes and Flux are very well documented with much tooling as well. Nix doesn't really have a working LSP or good code autocomplete, but with kubernetes, I can just start typing in a yaml file and then hit tab and it spits out the template for me. Code autocompletion with kubernetes feels much more similar to the tooling of other, more mature tooling
It's not as declarative as nix though. There are things missing, like OCI containers could theoretically shift if you don't rely on hashes and some other nitpicks. But declarativity is a spectrum, and I feel like, outside of scientific scenarios (think simulations where versioning, hardware, runtime etc being the same is very important), I think many non-nixos solutions are declarative enough.
Advice online seemed like i needed to basically create a nix flake for the app. I still havent gotten it installed because i have no idea what nix flakes are.
So, the problem is that flakes are technically an "experimental" feature, and thus are not allowed to be included as a primary solution in the official documentation. But, basically everybody uses flakes, so it leads to this crazy documentation split, and is a big part of why documentation on Nix is so part.
Some stuff can only be done with flakes, some stuff only with non-flakes and you have to figure out which is which on your own, while also dealing with the poor documentation for either.
The advice you received was wrong. You could also use a combination of a default.nix
file and a shell.nix
file to create a package and development environment for your app. But, the documentation is so poor that it's unlikely you will learn this, and figuring out how to do this on your own, is again, a massive time sink.
Some software is so complex and difficult that Debian does not maintain it on their own, and instead follows the upstream release cycle.
Browsers are one such example, and as you've discovered for me, Thunderbird is probably another.
Also, please do not recommend testing for daily usage. It does not receive critical security updates in a timely manner, including for things that would effect desktop users. Use stable, Sid, or another distro. Testing is for testing Debian ONLY, and by using Debian Testing, you are losing the advantage of immediate security fixes that come from literally any other distro.