Link android version number to pysollib.settings version number

[bwrightkc]

This change simply changes the android version number from being hardcoded in the buildozer file and instead links it to pysollib.settings so that there is no need to update the build version multiple times when version number increments.

[bwrightkc]

Version number was stuck at 3.4.1 in current source - wondering if this is why F-Droid was stuck at version 3.4.1 and didn't have the latest fix in it. Possibly relevant to #581 as that crash is fixed in 3.6.0 and may be the users are still experiencing the crash as F-Droid didn't see the 3.6.0 as a new release due to this line being outdated.

[joeraz]

I don't believe there is an automated job to update the Android version on F-Droid. It's usually @lufebe16 who handles these deployments - I'm not sure if I have the permissions to run it myself.

[lufebe16]

The F-Droid build is not an automatable process. Therefore, the version number for Android versions has been decoupled from the main system.

The Android app ID is org.lufebe16.pysolfc. Under this name, you can find the build specification for F-Droid at https://gitlab.com/fdroid/fdroiddata in the metadata directory.

The current procedure is as follows:

1. Add the new version number to ./buildozer/aversion
2. Create a release app. This generates important parameters for the release from the build system. The file ./buildozer/.buldozer/android/platform/.../dists/pysolfc/build/outputs/apk/release/output-metadata.json must be saved as pubspec.json in ./buildozer (update).
3. A changelog with the correct name for this version (as 'versioncode'.txt) must be created in ./fastlane/metadata/android/en_US/changelogs.
4. Check if everything is correct - then commit.
5. A new tag for the version number (android-x.x.x) can now be added to the commit. This triggers the F-Droid build.

Now wait. It takes about two weeks. The progress can be tracked with the
Android app F-Droid Build Status.

If something goes wrong, the build specification on fdroiddata may need to be updated and tested. This may also require communication with F-Droid developers.

If someone wants to take on this task, I have no objection.

[bwrightkc]

Ah, wow, that's on me then. Had no clue that F-Droid was still that involved on updates - I usually just load APKs directly. No point in this commit then :)

[joeraz]

I can try to run through those steps for 3.6.1 sometime in the upcoming week, if just because of the recent critical bugfixes, but I'd have to see about the long-term.

[lufebe16]

@joeraz Unfortunately, F-Droid has updated their build server from 'Debian Bookworm' to 'Debian Trixie'. A test with my build server in a container shows that further problems are to be expected. A third-party tool might also need to be updated. I'll take care of this myself after all. Thanks.

[joeraz]

@lufebe16 Understood, thanks. Should we merge this PR or just close it?

[bwrightkc]

Given what he said, my PR would not be helpful to the build process :)

…

On Jul 21, 2026, at 6:03 PM, Joe R. ***@***.***> wrote: joeraz left a comment (shlomif/PySolFC#584) <#584 (comment)> @lufebe16 <https://github.com/lufebe16> Understood, thanks. Should we merge this PR or just close it? — Reply to this email directly, view it on GitHub <#584?email_source=notifications&email_token=AICX5NK3UUYCBTDUJXVML6D5F7ZFLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTHE4TKNRXGEZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5039956713>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AICX5NMVHMK6YR4AVDD42EL5F7ZFLAVCNFSNUABDKJSXA33TNF2G64TZHMZTMNZYGY3DIO2JONZXKZJ3GQ4TCNBRGA2DGNJXUF3AE>. You are receiving this because you authored the thread.

[joeraz]

Alright, then.