Closed ltguillaume closed 1 year ago
Interesting, thanks for the observation. Unfortunately the documentation of f-droid server tool is basically non-exist and I never knew there is a setting that I can change for marking packages "stable" or not. I will see whether I can somehow find the property and change how their script write the server xml files.
I agree, F-Droid documentation and support is a mess: there's a lot of it, but it's fragmented and nothing is specific enough.
The F-Droid repo hasn't been updated for a month, how come?
Edit: Aaah wait, I didn't check the releases, apparently there's only been a new release since v96 6 days ago, perhaps the repos still have to be updated.
I've installed the new version directly from here now. Downside: I can't check if the problem described here would present itself again.
You can use Tobi823's great ffupdater to get releases directly from Github, it is the fastest way. I was a little busy after the holiday and also had some other commitments so the release got delayed a bit.
I can't check if the problem described here
No worries, I have F-Droid client on my phone and I can check myself.
Unfortunately F-Droid repo no longer functions.
Device info (please complete the following information):
Describe the bug While I briefly mentioned this in #104 I feel like a separate issue should be created for this, since it doesn't seem to be resolved.
For any of the updates coming out via the F-Droid ARM repo, I have to manually check for updates under the Versions header: F-Droid will never notify me of any updates, nor will will it consider listing newer versions as updates. The most probably cause for this is that none of the new versions available are ever marked as stable, so users will only be notified of new versions if they enable the expert option "Unstable updates".
This doesn't seem to be documented anywhere as the desired behavior, so I'm assuming this is an oversight.