me-web? 0.15.2: the first version in the F-Droid repository

- Nothing changes in the app. 0.15.1 never reached the F-Droid repository at packages.arasaka.software/fdroid/repo;
  this version is the first one there, so F-Droid, a store like it, or Obtainium can now find it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T9uhaCTSycTh1r8At679Pz
This commit is contained in:
thepraandClaude Opus 5.5 committed 2026-10-31 09:48:35 +01:00
1 parent 94cc74bb95
commit 1a548b4ead
3 files changed
+6 -3

No files matched your search

+2 -2
View File
@@ -19,10 +19,10 @@ patch=$(echo "$version" | cut -d. -f3)
code=$((major * 10000 + minor * 100 + patch)) code=$((major * 10000 + minor * 100 + patch))
tools/setup.sh --group fdroid tools/setup.sh --group fdroid
tools=$here/tools/fdroid/linux-x64 tools=$(cd "$here/tools/fdroid/linux-x64" && pwd -P)
pinned=$(sed -n 's/^fdroidserver==\([^ ]*\).*/\1/p' packaging/fdroid/requirements.txt) pinned=$(sed -n 's/^fdroidserver==\([^ ]*\).*/\1/p' packaging/fdroid/requirements.txt)
venv=$tools/fdroidserver-$pinned venv=$tools/fdroidserver-$pinned
if [ ! -x "$venv/bin/fdroid" ]; then if ! "$venv/bin/fdroid" --version > /dev/null 2>&1; then
rm -rf "$venv" rm -rf "$venv"
UV_CACHE_DIR=$tools/cache UV_PYTHON_INSTALL_DIR=$tools/python "$tools/uv-x86_64-unknown-linux-gnu/uv" venv -q --python 3.12 "$venv" UV_CACHE_DIR=$tools/cache UV_PYTHON_INSTALL_DIR=$tools/python "$tools/uv-x86_64-unknown-linux-gnu/uv" venv -q --python 3.12 "$venv"
UV_CACHE_DIR=$tools/cache "$tools/uv-x86_64-unknown-linux-gnu/uv" pip install -q --python "$venv/bin/python" --require-hashes -r packaging/fdroid/requirements.txt UV_CACHE_DIR=$tools/cache "$tools/uv-x86_64-unknown-linux-gnu/uv" pip install -q --python "$venv/bin/python" --require-hashes -r packaging/fdroid/requirements.txt
+3
View File
@@ -177,6 +177,9 @@ The Android release key: alias `meweb`, certificate SHA-256
release is published, so the repository can lag the release page but never lead it. `.gitea/scripts/fdroid.sh` release is published, so the repository can lag the release page but never lead it. `.gitea/scripts/fdroid.sh`
installs fdroidserver into `tools/fdroid` (cached like the JDK) with uv from `setup.json` and the hash-locked installs fdroidserver into `tools/fdroid` (cached like the JDK) with uv from `setup.json` and the hash-locked
`packaging/fdroid/requirements.txt`, because the box has no `ensurepip` and the apt package would bring 242 others. `packaging/fdroid/requirements.txt`, because the box has no `ensurepip` and the apt package would bring 242 others.
The environment is made at the cache's real path (`pwd -P`) and rebuilt whenever `fdroid --version` fails: its
scripts carry the absolute path they were made at, `tools/fdroid` is a symlink from a workspace that can move, and
0.15.1's step failed with `fdroid: not found` on exactly that.
It signs the repository with the APK's own key (`MEWEB_KEYSTORE_B64` and `MEWEB_KEYSTORE_PASS`, alias `meweb`), so It signs the repository with the APK's own key (`MEWEB_KEYSTORE_B64` and `MEWEB_KEYSTORE_PASS`, alias `meweb`), so
the F-Droid fingerprint is the certificate's `5F52CFF4…FDF846` and there is no second key to lose; it refuses any the F-Droid fingerprint is the certificate's `5F52CFF4…FDF846` and there is no second key to lose; it refuses any
other. It builds a new snapshot in other. It builds a new snapshot in
+1 -1
View File
@@ -1,6 +1,6 @@
<Project> <Project>
<PropertyGroup> <PropertyGroup>
<Version>0.15.1</Version> <Version>0.15.2</Version>
<Product>me-web?</Product> <Product>me-web?</Product>
<Company>Arasaka di Hvozdikov Yevheniy</Company> <Company>Arasaka di Hvozdikov Yevheniy</Company>
<Copyright>© 2026 Arasaka di Hvozdikov Yevheniy</Copyright> <Copyright>© 2026 Arasaka di Hvozdikov Yevheniy</Copyright>