Suggested version not calculated when "upstream version" is too old
Currently, I have the following versions of AnkiDroid from the main F-Droid repo listed:
- 2.2alpha17
- 2.2alpha14
- 2.2alpha1
But the current "upstream version" according to the metadata is version is 2.1.2. If no upstream version was in the metadata, then it would have selected version 2.2alpha17 as the default version. However, because an upstream version is available, it refuses to suggest a version that is higher than 2.1.2. As such, we get no suggested version at all, which means that the list of apps shows AnkiDroid without any version number (which looks strange when every single other app has a version number).
The solution is probably not to just take the latest version available (if we can't find a version <= upstream version). The problem with this is that we will start suggesting people upgrade AnkiDroid to 2.2alpha17 which is not desirable.
The solution is also not for the script which decides what to move to F-Droid Archive (currently anything more than 3 versions old), to also keep the latest stable release. The problem here is that the "latest stable release" really depends on compatibility with individual devices. Therefore, it cannot be calculated once for the entire repo.
Perhaps the solution is to do what we are currently doing, but to change the display in the app list. Is there some way it can be changed so that the fact that one or two apps don't have a version in the list doesn't stand out like a sore thumb?