Mises à jour sur F-Droid

Vous avez vu qu’il y avait une nouvelle version d’AntennaPod et vous vous interrogez :

  • Pourquoi la dernière version n’est-elle pas encore sur F-Droid ?
  • quand la nouvelle version sera-t-elle disponible sur F-Droid?

Due to the different steps and because we are not involved in publishing releases on F-Droid, we can’t tell when exactly the latest version will be available there.

En bref : cela peut prendre un certain temps. Nous vous demandons d’être patients.

Les étapes pour obtenir une nouvelle version sur F-Droid

  1. We release a beta version, which is only available through Google Play due to technical limitations in F-Droid.
  2. We do a slow, gradual roll-out to all Google Play users. That way we make sure that there are no critical bugs. This can take several weeks.
  3. We create a release on GitHub. We do this only after the roll-out on Google Play is complete.
  4. F-Droid systems check the AntennaPod repository and detect a new release. The update checker server runs daily (overnight in Europe).
  5. Après que F-Droid ait détecté une nouvelle version d’AntennaPod, il construit l’application. Ainsi, F-Droid s’assure que l’application que vous téléchargez correspond bien au code source publié par AntennaPod. Comme il y a beaucoup d’applications à construire, le serveur F-Droid prend 1 à 2 jours supplémentaires pour construire l’application.
  6. An F-Droid contributor signs the build cryptographically. To improve security, the contributor needs to take the app and physically walk it to a dedicated computer which is not connected to the internet. When all apps are signed, the contributor uploads them to the F-Droid systems. This usually takes 1 to 2 days.
  7. Vous avez vu qu’il y avait une nouvelle version d’AntennaPod et vous vous interrogez :

At this point we consider it ‘released on F-Droid’. But remember that your F-Droid client (the ‘app store’) also needs to refresh its local copy of the index. Only after that you’ll get prompted about the latest AntennaPod release.

So, what’s the ETA?

As you can see, there are a lot of steps which each take a varying amount of time. We usually take well over a month between releasing a beta version and tagging the release on GitHub. After the release is tagged, F-Droid usually takes four to six days to process it.

Ce que vous pouvez faire si la procédure prend plus de temps que prévu

Did we not tag the release on GitHub yet? Then please just wait. The update is in beta and not ready for public release.

We did tag the release on GitHub? As the F-Droid team notes: “don’t panic before 7 days have passed, please.”

  • Did those 7 days pass since we tagged the release on GitHub? Feel free to let us know by creating a post on our forum. We’ll take a look.
  • Did we tag the release 7 days ago or less? Then please just wait. Or investigate where we are in the process.

Investigate current status

If you want, you can follow these steps to get an idea of the progress:

  1. Check if and when the release was tagged on GitHub (you may need to hover, for example, ‘last week’ to see the exact date on GitHub). If so, it should soon be picked up by the update checker.
  2. Check if F-Droid’s AntennaPod versions list was updated since then. If so, it should soon be processed by the build server.
  3. Check if AntennaPod was built in the running cycle or the last cycle. You can also use the app F-Droid build status for this. If so, it should soon be cryptographically signed by an F-Droid contributor.
    • Note that there’s no queue for apps that need to be built. AntennaPod is not listed in the success and fail lists yet, and you want to know if it will be built?
      1. click on ‘fdroiddata version’ @ commit of a build cycle
      2. click on ‘Browse files’
      3. click on ‘Find file’
      4. Le paquet doit être de.danoeh.antennapod
      5. open the file
      6. check if it includes the latest release