indicate and point to the correct apk-repository at the website

i just found an issue which is or will be somehow related but nothing similar: fdroid-website#57

there are some apps which are only available at the archive-repo like https://f-droid.org/packages/com.ghostsq.commander.sftp/, https://f-droid.org/packages/net.osmand.parkingPlugin/ or https://f-droid.org/packages/net.osmand.srtmPlugin.paid/ for now.

thankfully they can be searched for and are shown at the homepage, but there are 2 things which should be addressed IMHO:

• an indicator in which repository it (or to be precise every apk or at least the latest/starred apk) can be found would make sense. maybe a hint per apk like in the fdroid-app, but if so with an additional easily visible "general-indicator" for the the latest/starred apk to notice that i have to activate an other/additional repository after installing fdroid.

  since i have to deal with and assist not so tech-savvy users which were really desperate and nearly leaving fdroid, because they couldn't find a desired app to install on a new phone but it was clearly visible on the homepage, this will be a huge relief.

• and therewith we are at the second point which is more of an existing bug:

  at the website of the corresponding "archive-app" all apk-links for sideloading point to https://f-droid.org/REPO/<app-name_versioncode>.apk instead of https://f-droid.org/ARCHIVE/<app-name_versioncode>.apk and therefore you only get an 404-error. - so also sideloading also didn't work for the pitiful noobs.

i'm pretty sure a bunch of gitlab-issues are only created because of these issues, like fdroiddata#823 (closed) or fdroiddata#822, fdroiddata#909, fdroiddata#908 or fdroiddata#888.

@DJCrashdummy Is there a reason why you opened the issue against the fdroidserver repo, not the website repo?

@Bubu yes, because the website says so: https://f-droid.org/issues/

at fist i was skeptical (and i am still so), but in the third abstract it is clearly stated:

issues relating to the web site...

changed the description

Oh... there is actually an issue about fixing this: fdroid-website#12

:D

moved from fdroidserver#393 (closed)

Moving actually to the Jekyll Plugin tracker because I think this needs to be fixed here. Related to #16, not sure if the issues can't just be merged together.

i'm not sure if it is here the right place, maybe fdroid-website suits better, because

• in your linked issue there is a line

For the use case of making a custom webview of multiple repositories, we have Repomaker. So we shouldn't duplicate that here in the jekyll plugin.

• then it is also a little bit of a website-design suggestion...

• and my second point is (for sure related, but) an actual appearing bug!

The jekyll plugin (afaik) generates each app page, so the bug with the wrong urls being linked should be located here.