@fdroidorg
oh, you are exactly right! #sdkmanager installed #aapt2 with wrong architecture. 😮
i thought there would be like <1% chance anyone would have any idea.
thanks for the help! 😍 i'm hoping to have something to publish on #fdroid in not too long.
thank you!!!
Some #Android #SDK packages are updated with a revision number, but #sdkmanager does not allow installs to use that revision number. This sometimes breaks #ReproducibleBuilds. There is an issue open since 2017 about this:
https://issuetracker.google.com/issues/38045649
If anyone wants this feature, it should be easy to implement in #FDroid's sdkmanager:
https://gitlab.com/fdroid/sdkmanager/-/issues/26
Wer Probleme mit dem Jetson und Docker hat das er nach einen "apt upgrade" und Docker Version 28.0.X nicht mehr läuft, gibt es hier die Lösung: https://forums.developer.nvidia.com/t/another-solution-with-iptables-raw-issue/328477
Continuing the discussion from Docker fail to start jetson nano after clean install of jetpack 6.2 (fix it): Hello everyone, I found a solution to install Docker version 28.0.X on the Jetson. sudo mkdir -p /etc/systemd/system/docker.service.d sudo nano /etc/systemd/system/docker.service.d/override.conf Add the following content: [Service] Environment="DOCKER_INSECURE_NO_IPTABLES_RAW=1" Then reload and restart the Docker service: sudo systemctl daemon-reload sudo systemctl restart doc...
In the official release of the #AndroidSDK package "build-tools_r35.0.1_linux.zip", they included what looks like a hand-edited "source.properties" metadata file that is a key part of the "sdkmanager" packaging system:
```
Pkg.UserSrc=false
Pkg.UserSrc=false
Pkg.Revision=35.0.1
#Pkg.Revision=35.0.0 rc4h
```
I mean really? The Android SDK packages are not automatically generated?
brainwashed by lentils
Hans-Christoph Steiner
Joachim 🍀