[BUG] Orbot very out of date in provided custom Fdroid repo

[kraftnix]

Describe the Bug The latest version of Fdroid available from https://guardianproject.info/fdroid/repo is 16 months old (17.2.1-RC-1-tor-0.4.8.7).

To Reproduce Steps to reproduce the behavior:

1. Add Fdroid repo at: https://guardianproject.info/fdroid/repo
2. Find Orbot
3. See that the version is very very old

Expected Behavior A relatively up-to-date version of Orbot should be available.

What Custom Configuration Do You Use? If applicable, how did you set up Orbot? Did you configure some settings?

Smartphone (please complete the following information):

• Device: Pixel
• OS: Android 15 - GrapheneOS
• Version: 2025060200

Additional Context There are many similar issues in this repo which have been recently closed.

Is the custom FDroid repo intended to be supported? If not can we have clarity? It is quite unacceptable to have security critical software like Orbot be so out of date.

[shivagnihotri]

I fully agree. It should be bleeding edge.

[Hasshu]

Might as well just ditch that insecure repo altogether in favor of Accrescent.

[n8fr8]

We are rolling out our latest RC this week on the GP F-droid repo: https://github.com/guardianproject/orbot-android/releases/tag/17.5.0-RC-1-tor-0.4.8.16

along with improved automation to make sure the releases are available more quickly.

[kraftnix]

This is still problematic... Fdroid is still showing a release 17.5.0 release which is months old.

The only reasonable way to use Orbot at the moment is Obtainium.

If the Fdroid repo will be permanently out of date by months of sometimes years (as when I opened this issue). It should be removed and not recommended at all.

[n8fr8]

We have automation in place to grab the "orbot-latest" from our releases folder: https://gitlab.com/guardianproject/wind/fdroid-metadata/-/blob/master/download-orbot-update.sh?ref_type=heads

We will be updating this soft link soon to our new RC: https://guardianproject.info/releases/orbot-latest.apk